From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Access to Intermediate Document after Pre-processing
Date: Wed, 3 Aug 2016 16:20:47 +0200 [thread overview]
Message-ID: <1e6ed1d4-58eb-2363-9d6d-298e409dd3bc@gmail.com> (raw)
In-Reply-To: <0F6C343B-F316-4716-BCE2-A8398FF23B1C@smartward.com.au>
On 08/03/2016 03:25 PM, Malte Stien wrote:
> Hi all,
>
> I am working with a reasonably complex document structure, where I make heavy use of the following constructs
>
> \input (to import a number of source files)
> \if and \newif (to switch between different paragraphs depending on some conditions)
> \setvariable and \getvariable (to reuse some text in different places)
>
> So, does ConTeXt run some sort of pre-processing step that processes all of the above and which results in an intermediate document that is then type-set? And is it possible to only run this pre-processing step and get access to that intermediate document?
This is a TeX thing. Unfortunately, TeX does not have any introspection into the expansion processor which is why you cannot preprocess your source files as, e.g., with the C preprocessor. You might be able though to hook into the process_input_buffer callback and craft your preprocessed file by hand.
>
> I am asking as I have some Ruby scripts that take ConTeXt documents and convert it to another format. However, those scripts do not deal with any of the above and rather than implementing the necessary logic to deal with importing of files, conditions and variables, I thought ConTeXt does that already if only I could get access to the resulting intermediate file.
>
> Does that makes sense?
>
> Thank you,
> Malte.
Cheers, Henri
>
> Malte Stien, PhD | Chief Technology Officer | SmartWard Pty Ltd
> E: malte.stien@smartward.com.au | W: www.smartward.com.au
> P: +61 (0)2 6251 1798 | M: +61 (0)413 928 895
> -- Please consider the environment before printing this email --
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-08-03 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 13:25 Malte Stien
2016-08-03 14:20 ` Henri Menke [this message]
2016-08-08 11:59 ` Hans Hagen
2016-08-08 12:00 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e6ed1d4-58eb-2363-9d6d-298e409dd3bc@gmail.com \
--to=henrimenke@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).