J.Pietschmann wrote:
Maybe I'm wrong in trying to do so, but I'd like to handle both
formatting objects in the same way.
If page numbers can be resolved to strings early, it should be
done. All the hassle for space readjusting, and perhaps reflowing
content, should be reserved for forward
Luca Furini wrote:
The Knuth-style page breaking algorithm gets a representation of a whole
page-sequence
Ah, I wasn't aware of this. Well, operating on a whole page
sequence makes implementing widows/orphans and other keep
conditions possible without backtracking, interesting.
Very
On 29.08.2005 01:51:21 Stephen Denne wrote:
Luca Furini wrote:
The method PageNumberCitationLM.get() allocates the width of
the string
MMM if the id is not already known;
Could a FOP extension element be added to indicate how many pages the
document is likely to be, and allocate
J.Pietschmann wrote:
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?
This could work for page-numbers but not for
Firstly, thank you all for your suggestions.
All your interesting replies led me to this conclusion:
- in most cases, it is enough to make some local adjustments in each line
containing page-numbers or page-number-citations;
- sometimes, when a particularly elegant output is needed, it would
There is a layout problem with fo:page-number and fo:page-number-citation,
already pointed out but still unresolved.
I think, these formatting objects are very similar, even if their actual
handling is quite different: they both must be replaced by an information
(a page number) that is (or
Luca Furini wrote:
snip/
The computation, in itself, is easy, as the LineLM already has all the
necessary information: line width, unadjusted width, available stretch
and shrink.
I think shrinking/stretching the spaces in the case where the guessed
space doesnt match the actual is an
Luca Furini wrote:
Yes, undoubtedly a two-pass rendering would produce a better output: and
after all, even LaTex needs to be run twice if there are page number
citations.
Backtracking with some attempts to minimize the scope for
re-layout should be enough, though somewhat less
