You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Jan Tosovsky (JIRA)" <ji...@apache.org> on 2015/08/25 14:14:46 UTC

[jira] [Commented] (FOP-2520) Empty elements consume space

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

Jan Tosovsky commented on FOP-2520:
-----------------------------------

Have you formatted the code above? There is white space between multiple <fo:wrapper> elements which seems to be preserved which is IMO correct. Multliple indexterms in Docbook source shouldn't be delimited with anything (but some editors like XMetal do this, so extra post processing - space removal, is required). For XEP the generated XSL-FO source differs as there are custom XEP tags instead.

> 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)