Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-18 Thread Andreas Schneider
Hans Hagen wrote: > as it takes less time wrting a helper than explaining how to do it i > just added it as feature (a few years from probably only wolfgang > remembers that it's there) > > i'll upload a beta to the website that provides ... > > \starttext > > \dorecurse {100} { > test \foo

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-17 Thread Hans Hagen
On 17-1-2010 23:13, Andreas Schneider wrote: dealing with multipass data in mkiv is completely different from mkii and at some point there will be a proper api for users (makes no sense now as i might as well change internals along with luatex developments) in mkiv we store info in tables and mu

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-17 Thread Martin Schröder
2010/1/17 Andreas Schneider : > What I need would be a precise page break handling. Currently ConTeXt seems > to process a whole paragraph as one object, and then breaks it down to > individual pages. That leads to a problem however: This is how TeX works. :-) Best Martin

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-17 Thread Andreas Schneider
> dealing with multipass data in mkiv is completely different from mkii > and at some point there will be a proper api for users (makes no sense > now as i might as well change internals along with luatex developments) > > in mkiv we store info in tables and much is available during a document > r

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-17 Thread Hans Hagen
On 17-1-2010 22:16, Andreas Schneider wrote: 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 t

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-17 Thread Andreas Schneider
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 > exp

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-17 Thread Hans Hagen
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

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-16 Thread Andreas Schneider
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 cas

Re: [NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-16 Thread Wolfgang Schuster
Am 16.01.2010 um 17:53 schrieb Andreas Schneider: > Hi, > > I'm using \appendtoks...\to\everyaftershipout to reset a variable on every > pagebreak. This doesn't work as I expect(ed) it, since it seems to only > trigger after a paragraph. The following example shows the problem. On every > new

[NTG-context] \everyaftershipout isn't "called" for every pagebreak

2010-01-16 Thread Andreas Schneider
Hi, I'm using \appendtoks...\to\everyaftershipout to reset a variable on every pagebreak. This doesn't work as I expect(ed) it, since it seems to only trigger after a paragraph. The following example shows the problem. On every new page, the first footnote should be "New", which is not the case