Luca Furini wrote:
PageNumberLM.get() calls getCurrentPV().getPageNumberString(), but, as pagination is performed later, it always get the page-sequence initial page number
In the maintenance branch, the formatted page number string was produced just as a new page was set up. I wonder whether the page sequence LM can put the current page number string into the layout context? After all, when a page break is accepted, control returns to the page sequence LM in order to finalize the area subtree for the page, at this point is should be possible to adjust the page number string for the next page.
I don't like 1 very much, because I think the creator LM is not a significant attribute of an area, but 2 involves adding many attributes too (and maybe even less significant!) ...
The attributes could be bundeled in a Java object, and the line area only holds a pointer to it (null if not relevant). Another (somewhat abberant) idea is to store the values in the area for the page number citation, and a line area had to check for page number citation area descendants for reformatting. Unfortunately, I recently got an email with a real life example where expanding page number citations lead to a line break (in a book index), so adjusting the line area might not be enough. J.Pietschmann
