I will do my best, but I see nothing in the generated fo that strikes me
as suspicious.
See other post
<http://apache-fop.1065347.n5.nabble.com/trouble-with-fonts-size-running-from-command-line-tp36281.html>
on not getting identical output from commandline, which is hampering
generating reliable tests.
Anecdote: prior to the 3 pages of stutter there are three pages
(correctly numbered) which have no text (entirely region-before), so
this may also be related to issue
<http://apache-fop.1065347.n5.nabble.com/generating-pdf-fails-depending-on-page-layout-order-tp16726.html>
If you're anxious for an example, I can certainly post the 40-page
chapter fobut the last one made Vincent um, er, grumpy :).
rjs
On 07/12/2012 02:35 AM, Pascal Sancho wrote:
Hi,
One needs to see what there is in the XSL-FO (XML + XSLT transfo
result) fed to FOP.
Can you have a look on it, or provide a minimal version of it, so one
can reproduce the described issue?
2012/7/11 Rob Sargent <[email protected]>:
In the middle of my document that page numbering goes 19, 20, 24,24,24,24,
25. Further more the table-of-contents generated by fo:page-number-citation
uses the bogus 24s for elements on actual page 21,23.
Anyone seen this before? Hints on rooting out the cause?
FOP-1.0
rjs
