From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Andreas Schneider <aksdb@gmx.de>
Subject: Re: \everyaftershipout isn't "called" for every pagebreak
Date: Sun, 17 Jan 2010 21:42:04 +0100 [thread overview]
Message-ID: <4B53761C.3070106@wxs.nl> (raw)
In-Reply-To: <hitcq2$q57$1@ger.gmane.org>
On 16-1-2010 22:58, Andreas Schneider wrote:
> Wolfgang Schuster wrote:
>>
>> This can't work because TeX collects mote material than it needs for the
>> current page and the same happens with the footnotes, the only thing you
>> can do is to use two pass data
>>
>> Wolfgang
>
> Is there not even some event in Lua that could be used to handle this case?
> I think MkIV compatibility is all I need.
> In case this is also not possible: can you give me a hint where to learn
> more about twopass processing? Is there in MkIV still something that
> requires two (or more) passes that I could take a look at to learn how to do
> it? (I guess I can understand Lua easier than plain TeX, so I guess MkII is
> out of the picture.)
It depends on your document. We have workflows where we can do with one
pass in which case we run with --once (--runs=2 or so)
Future versions of context mkiv might need one run less (in some cases)
or one perceived run (which saves startup cycles) but as Wolgangs
explained already, in more complex cases we cannot do with less runs as
any change haping now can influence something a few pages back which in
turn might influence what follows.
Normally, when you correct only typos there will be no multiple runs.
MkIV already is more efficient as we now always assume an advanced pdf
backend so that we don't need to use the MkII the object reference
mechanism.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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:[~2010-01-17 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 16:53 Andreas Schneider
2010-01-16 20:00 ` Wolfgang Schuster
2010-01-16 21:58 ` Andreas Schneider
2010-01-17 20:42 ` Hans Hagen [this message]
2010-01-17 21:16 ` Andreas Schneider
2010-01-17 21:45 ` Hans Hagen
2010-01-17 22:13 ` Andreas Schneider
2010-01-17 22:25 ` Martin Schröder
2010-01-17 22:59 ` Hans Hagen
2010-01-18 12:12 ` Andreas Schneider
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=4B53761C.3070106@wxs.nl \
--to=pragma@wxs.nl \
--cc=aksdb@gmx.de \
--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).