[ 
https://issues.apache.org/jira/browse/FOP-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071659#comment-14071659
 ] 

Robert Meyer commented on FOP-2374:
-----------------------------------

I've been taking a look at this. Since it's in the layout engine it goes 
without saying that it's not the easiest thing to diagnose and fix but my guess 
would be it's an issue with the InlineKnuthSequence.addALetterSpace method. If 
you comment out the removeLast() from that method it leaves the space along 
with some others added during the layout process. The method removes those 
extra spaces correctly but is I imagine being too greedy and removes the valid 
one in the string as well. I've yet to fully understand the logic going on here 
but will keep this updated if I find more time to look at this and make some 
more progress.

> space missing before fo:page-number-citation-last in PDF output
> ---------------------------------------------------------------
>
>                 Key: FOP-2374
>                 URL: https://issues.apache.org/jira/browse/FOP-2374
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/pdf
>    Affects Versions: 1.1
>            Reporter: Jason Harrop
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: _test.fo
>
>
> When you generate a PDF from FO such as:
> <fo:block><fo:inline>of </fo:inline><fo:page-number-citation-last 
> ref-id="page2"/></fo:block>
> the whitespace between the word "of" and the page-number-citation-last 
> element is lost.
> In 
> http://apache-fop.1065347.n5.nabble.com/preserving-a-trailing-space-in-inline-td40644.html
>   Pascal Sancho 
> diagnosed that the issue arises when a fo:page-number-citation-last (PNCL) 
> comes after a fo:inline element
> and no content comes after the PNCL.
> He also identified a workaround: "Just add a character AFTER the PNCL element 
> other than a regular white space"
> I'm also attaching his test FO file



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to