Hi Rob,

Thanks for your efforts to reduce the size of the FO file, this is
really appreciated.

I believe I found the problem, but need to investigate a bit more. In
the meantime, try to modify the content so that it doesn’t overflow the
page. Watch for messages saying ‘Content overflows the viewport of the
fo:region-body on page n’. Except that ‘n’ is not the page number... but
the column number!

If you can avoid page overflows, you should avoid triggering the issue
and get appropriate page numbers.

HTH,
Vincent


On 19/07/12 20:33, Rob Sargent wrote:
> I have whittled the fo down further (shorter-fop.xml, now 35%) of original,
> but this is as small as I can go to reproduce the exact 3-page stutter.  I can
> remover one more page and get a single stutter (shortest-fop.xml)
> 
> I pray this will be enough.
> 
> Thanks a bunch.
> 
> 
> On 07/19/2012 12:51 PM, Rob Sargent wrote:
>> I truly regret the large fo;  I know it hampers things at debug time.  I had
>> to find a particular starting point such that the content was still aligned
>> with the original placements.  I'll try to trim more pages from after the
>> page numbering problem.
>>
>> rjs
>>
>>
>> On 07/19/2012 01:31 AM, Pascal Sancho wrote:
>>> Hi,
>>>
>>> To be efficient, a short fo helping to reproduce the issue should be
>>> attached to the bug entry, so opening a bug rather than ask on this
>>> list doesn't help anymore if the material remains the same.
>>> I (or somebody else) have to look closer into the fo you attached
>>> here,  then perhaps I (or somebody else) will, or will not, find a bug
>>> causing this issue. Since the use case is quite big, that will take
>>> some extra time :/
>>>
>>> 2012/7/18 Rob Sargent <rsarg...@xmission.com>:
>>>> My apologies, but I've been unable to shrink this to a small test.  I'm
>>>> forced to send a rather large fo, but that's my level of desperation. Or
>>>> should I open a bug report?
>>>>
>>>> rjs
>>>>
>>>>
>>>>
>>>>
>>>> On 07/12/2012 09:20 AM, Rob Sargent wrote:
>>>>
>>>> I will do my best, but I see nothing in the generated fo that strikes me as
>>>> suspicious.
>>>>
>>>> See other post 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
>>>>
>>>> If you're anxious for an example, I can certainly post the 40-page chapter
>>>> fo but 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 <rsarg...@xmission.com>:
>>>>
>>>> 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
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>>
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Reply via email to