Pascal Sancho commented on FOP-2520:

All text nodes are processed by FOP, this is the correct behaviour.
If you want to discard spaces, you have to 1st do it at XSLT stage:
 - avoid indentation
 - do not add unwanted extra white spaces (including linefeed)
 - etc.

At FOP stage, you may interact on white spaces using following FO properties:
 - linefeed-treatment (http://www.w3.org/TR/xsl/#linefeed-treatment)
 - white-space-treatment (http://www.w3.org/TR/xsl/#white-space-treatment)
 - white-space-collapse (http://www.w3.org/TR/xsl/#white-space-treatment)

That said, Jira is not the right place to discuss about this.
either fop-users mailing list, or better XSLT/XSL-FO mailing lists, are more 
Audience on such lists is larger.

> 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

Reply via email to