From: Andreas Schneider <aksdb@gmx.de>
To: ntg-context@ntg.nl
Subject: Re: \everyaftershipout isn't "called" for every pagebreak
Date: Sun, 17 Jan 2010 22:16:41 +0100 [thread overview]
Message-ID: <hivunp$2j4$1@ger.gmane.org> (raw)
In-Reply-To: <4B53761C.3070106@wxs.nl>
Hans Hagen wrote:
> 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
In my example I can't even get \pagenumber to work correctly. If I replace
my \test macro with \pagenumber, the first 4 pages all print page "1" (since
it's still the same paragraph). Is there anything I can do about that? (Of
course my main concern is the original problem of not catching page breaks
to reset a variable).
I also can't quite work out a multi-pass solution ... the only way I could
imagine how it could work is by storing the content I would like to print
together with the coordinates it was printed to in the first run, and in the
second run evaluate from these information when a page break occured and
modify the data accordingly. But I'm a bit lost here where to start ... my
TeX knowledge is rather basic and I don't know anything about the luatex
internals so I don't know if there are any events I could hook (and when and
where to hook them :-/).
I would be very grateful if you could point me in a direction I can work
forward from - I can only guess that there are similar mechanisms in the
already existing MkIV code ... although the \pagenumber problem seems to
indicate that it might be near to impossible :-/
Best Regards,
Andreas.
___________________________________________________________________________________
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 21:16 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
2010-01-17 21:16 ` Andreas Schneider [this message]
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='hivunp$2j4$1@ger.gmane.org' \
--to=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).