Alexey Neyman commented on FOP-1444:

A while ago I raised the same issue on the fop-users mailing list and got the 
following response:

Behavior is related to xml blanks (white-space, line-feed, etc.) that are
before or after fo:inline tags.

You should avoid to use fo:inline when it is not required (replacing it
with fo:wrapper when it is just used as properties carrier), or avoid to
get extra blanks in your resulting xsl-fo.
The latter can be done by surrending all constant strings with xsl:text
element in XSLT.

The attached test case has the same issue: single space before <fo:leader>. 
Funny thing is, this bug was submitted against FOP 0.94. As I mentioned in the 
email thread referenced above, space next to fo:leader worked fine in FOP 1.0, 
but again produced misaligned output in FOP 1.1.

Could anyone clarify whether FOP's handling of whitespace is a bug (and 
"avoiding whitespace" is a workaround), or was it intentional change in FOP 1.1?

> PDF table of contents generated with incorrect page number alignments
> ---------------------------------------------------------------------
>                 Key: FOP-1444
>                 URL: https://issues.apache.org/jira/browse/FOP-1444
>             Project: Fop
>          Issue Type: Bug
>          Components: pdf
>    Affects Versions: 0.94
>         Environment: Operating System: Windows XP
> Platform: PC
>            Reporter: David H. Gutteridge
>         Attachments: FOP_TOC_Bug_Test.dbk, FOP_TOC_Bug_Test.fo, 
> FOP_TOC_Bug_Test.pdf
> It seems there's a threshold where FOP does not align page number references
> correctly when generating tables of contents in PDF documents.  I see that you
> have a reference to this in your FAQ (question 3.10), but it says "The most
> recent FOP releases should have this problem fixed", I'm seeing this problem
> with 0.94.
> (I have a sample FO document I will attach, looks like the initial bug 
> reporting
> interface doesn't let me do this.)

This message was sent by Atlassian JIRA

Reply via email to