[
https://issues.apache.org/jira/browse/FOP-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14714197#comment-14714197
]
Björn Kautler commented on FOP-2520:
------------------------------------
Ah, the profiling xsl had {{indent="yes"}} for {{xsl:output}} and thus
formatted the output.
But I'm still unsure whether this is correct behaviour of FOP.
Shouldn't the space be insignificant in XML except within a text node?
I guess the problem is, that in this case there is mixed content, but afair the
parsed XML should have
{noformat}
<fo:block>-node
text-node without anything but whitespaces, or maybe even with empty
text
<fo:wrapper>-node
text-node without anything but whitespaces, or maybe even with empty
text
<fo:wrapper>-node
text-node without anything but whitespaces, or maybe even with empty
text
<fo:wrapper>-node
text-node without anything but whitespaces, or maybe even with empty
text
<fo:wrapper>-node
text-node with "You can customize most tables in the product..."
{noformat}
So shouldn't the empty text nodes be ignored instead of producing a slight
offset (without any characters like space character added) in the produced PDF
each?
> Empty elements consume space
> ----------------------------
>
> Key: FOP-2520
> URL: https://issues.apache.org/jira/browse/FOP-2520
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Björn Kautler
> Attachments: empty space that should not be there.png
>
>
> If you use {{indexterm}} tags in DocBook, the DocBook XSL stylesheets
> generate empty {{fo:wrapper}} or {{fo:block}} elements with an {{id}}
> attribute. These elements take up visible space if processed with FOP. Using
> XEP, those empty tags do not consume any space.
> Here an example excerpt from a FO file in question and [attached|^empty space
> that should not be there.png] the result.
> {code:xml}
> <fo:block space-before.optimum="0.6em" space-before.minimum="0.4em"
> space-before.maximum="0.8em">
> <fo:wrapper id="N1004F"><!--table, customize columns--></fo:wrapper>
> <fo:wrapper id="N10056"><!--customize, table--></fo:wrapper>
> <fo:wrapper id="N1005D"><!--filter, table--></fo:wrapper>
> <fo:wrapper id="N10064"><!--table, filter--></fo:wrapper>You can customize
> most tables in the product. The configured table view is saved in your user
> profile and will be restored when you start the prouct the next time.
> </fo:block>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
