Thanks! Our stylesheets indeed added one space before and after fo:leader, to
separate it from the title and page numbers. Converting that to
padding-{left,right} properties on fo:leader solved the misalignment issue.
Just out of curiosity, was the misalignment caused by a stricter
interpretation of XSL-FO specification by FOP 1.1, or is it a bug in FOP that
can be worked around by not using whitespace before/after fo:leader?
Regards,
Alexey.
On Tuesday, April 02, 2013 05:22:32 am Pascal Sancho wrote:
> Hi,
>
> 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.
>
>
> 2013/3/31 Alexey Neyman <[email protected]>
>
> > **
> >
> > Hi all,
> >
> >
> >
> > I've noticed that since the upgrade from FOP 1.0 to FOP 1.1, the page
> > numbers in the Table of Contents are misaligned. Attached is XSL-FO
> > input, and two PDFs, produced by FOP 1.0 and FOP 1.1.
> >
> >
> >
> > Also attached are a couple of images, magnified screenshot of the
> > resulting PDFs with a vertical line close to the page numbers to show
> > misalignment more clearly.
> >
> >
> >
> > Could you please have a look at what's causing this misalignment?
> >
> >
> >
> > Thanks,
> >
> > Alexey.
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
