From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Access to Intermediate Document after Pre-processing
Date: Mon, 8 Aug 2016 13:59:53 +0200 [thread overview]
Message-ID: <57ae8542-0f37-da48-da91-80d8d931804d@wxs.nl> (raw)
In-Reply-To: <1e6ed1d4-58eb-2363-9d6d-298e409dd3bc@gmail.com>
On 8/3/2016 4:20 PM, Henri Menke wrote:
> 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)
are you sure that there are no mechanism already built in context that
can be of help? (of just lua)
>> 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.
apart from severe performance issues, such introspection has not much
advantage as you then end up with interpreting something that either has
lost information or get information that is already available otherwise
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-08 11:59 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
2016-08-08 11:59 ` Hans Hagen [this message]
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=57ae8542-0f37-da48-da91-80d8d931804d@wxs.nl \
--to=pragma@wxs.nl \
--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).