[
https://issues.apache.org/jira/browse/FOP-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Sancho closed FOP-2520.
------------------------------
Resolution: Invalid
Hi,
text nodes are taken into account by both FOP and XEP.
if you want to discard spaces, you have to do it by yourself at XSLT stage,
depending on what XSLT engine (and options) you are using (FOP comes with Xalan
for convenience, but your may use your own).
As a good practice, you should not mix text nodes and FO elements in your XSLT
template, this prevent Xalan (or other) to keep blank text nodes in final
XSL-FO:
use an xsl:text to wrap the text "You can customize ... the next time.", and
all blank text nodes will magically disappear.
> 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)
