Björn Kautler (JIRA | 2 Sep 11:13 2015
Picon

[jira] [Commented] (FOP-2522) Soft hyphens in front of some characters are transformed to hyphen-minus


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

Björn Kautler commented on FOP-2522:
------------------------------------

Further characters where I have seen it happen:
- Solidus (http://decodeunicode.org/u+002F)
- CRLF (http://decodeunicode.org/u+000D + http://decodeunicode.org/u+000A)
- Question Mark (http://decodeunicode.org/u+003F)
- Right curly bracket (http://decodeunicode.org/u+007D)

> Soft hyphens in front of some characters are transformed to hyphen-minus
> ------------------------------------------------------------------------
>
>                 Key: FOP-2522
>                 URL: https://issues.apache.org/jira/browse/FOP-2522
>             Project: FOP
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Björn Kautler
>
> If you have a verbatim block like {{<programlisting>}} in DocBook, the DocBook XSL stylesheets insert
many soft hypens (http://decodeunicode.org/u+00AD) into the content to show where the FO-processor
may insert linebreaks. By default after spaces and non-breakable spaces, but configurable also after
arbitrary other characters.
> Unfortunately it seems FOP does not handle the soft hyphens correctly, depending on the character that
follows it. Soft Hyphens in front of some characters are transformed to hyphen-minus, no matter what
(Continue reading)

Björn Kautler (JIRA | 29 Aug 02:27 2015
Picon

[jira] [Created] (FOP-2522) Soft hyphens in front of some characters are transformed to hyphen-minus

Björn Kautler created FOP-2522:
----------------------------------

             Summary: Soft hyphens in front of some characters are transformed to hyphen-minus
                 Key: FOP-2522
                 URL: https://issues.apache.org/jira/browse/FOP-2522
             Project: FOP
          Issue Type: Bug
    Affects Versions: 2.0
            Reporter: Björn Kautler

If you have a verbatim block like {{<programlisting>}} in DocBook, the DocBook XSL stylesheets insert
many soft hypens (http://decodeunicode.org/u+00AD) into the content to show where the FO-processor
may insert linebreaks. By default after spaces and non-breakable spaces, but configurable also after
arbitrary other characters.

Unfortunately it seems FOP does not handle the soft hyphens correctly, depending on the character that
follows it. Soft Hyphens in front of some characters are transformed to hyphen-minus, no matter what
hyphenation-characters is configured and even if the occurence is within a line and not at line break.

I've observed this behaviour with soft hyphens in front of apostrophe
(http://decodeunicode.org/u+0027), quotation mark (http://decodeunicode.org/u+0022),
hyphen-minus (http://decodeunicode.org/u+002D) and full stop (http://decodeunicode.org/u+002E)

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Tony Graham | 28 Aug 16:22 2015
Picon

'Validating XSL-FO' on FOP website

Please consider adding 'focheck' (https://github.com/AntennaHouse/focheck)
to the set of schemas listed on the FOP website at
http://xmlgraphics.apache.org/fop/fo.html#fo-validate

Regards,

Tony Graham.

Joery Mens (JIRA | 28 Aug 09:05 2015
Picon

[jira] [Updated] (FOP-2521) Letter-spacing + Arial-font is not always applied


     [
https://issues.apache.org/jira/browse/FOP-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joery Mens updated FOP-2521:
----------------------------
    Attachment: reproduce.fo
                pdf2.0.pdf
                pdf1.1.pdf
                pdf1.0.pdf
                arial.ttf

> Letter-spacing + Arial-font is not always applied
> -------------------------------------------------
>
>                 Key: FOP-2521
>                 URL: https://issues.apache.org/jira/browse/FOP-2521
>             Project: FOP
>          Issue Type: Bug
>    Affects Versions: 1.1, 2.0
>            Reporter: Joery Mens
>         Attachments: arial.ttf, pdf1.0.pdf, pdf1.1.pdf, pdf2.0.pdf, reproduce.fo
>
>
> The letter-spacing attribute worked correct in FOP 1.0; However in FOP 1.1 and FOP 2.0 it is not applied
when the text-content contains specific letter combinations. It seems to fail when a capital letter 'V'
is used in combination with a small letter.
> In the attachments you see the PDF's generated with FOP1.0, 1.1 and 2.0, the used xslfo and the used font-file.

--
(Continue reading)

Joery Mens (JIRA | 28 Aug 09:04 2015
Picon

[jira] [Created] (FOP-2521) Letter-spacing + Arial-font is not always applied

Joery Mens created FOP-2521:
-------------------------------

             Summary: Letter-spacing + Arial-font is not always applied
                 Key: FOP-2521
                 URL: https://issues.apache.org/jira/browse/FOP-2521
             Project: FOP
          Issue Type: Bug
    Affects Versions: 2.0, 1.1
            Reporter: Joery Mens

The letter-spacing attribute worked correct in FOP 1.0; However in FOP 1.1 and FOP 2.0 it is not applied when
the text-content contains specific letter combinations. It seems to fail when a capital letter 'V' is
used in combination with a small letter.

In the attachments you see the PDF's generated with FOP1.0, 1.1 and 2.0, the used xslfo and the used font-file.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Pascal Sancho (JIRA | 27 Aug 16:12 2015
Picon

[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=14716732#comment-14716732
] 

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 appropriate.
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
(Continue reading)

Björn Kautler (JIRA | 26 Aug 17:45 2015
Picon

[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=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
(Continue reading)

Björn Kautler (JIRA | 26 Aug 16:41 2015
Picon

[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=14713551#comment-14713551
] 

Björn Kautler commented on FOP-2520:
------------------------------------

Ah, thanks for your help guys.
Actually it is the preprocessing of the file.
The profiling step we do before the DocBook->FOP for making the Doku customer- and build-specific
actually inserts newlines between the <indexterm>s, so the input DocBook for the DocBook XSL is

{noformat}
         <para>
            <indexterm significance="normal">
               <primary>table</primary>
               <secondary>customize columns</secondary>
            </indexterm>
            <indexterm significance="normal">
               <primary>customize</primary>
               <secondary>table</secondary>
            </indexterm>
            <indexterm significance="normal">
               <primary>filter</primary>
               <secondary>table</secondary>
            </indexterm>
            <indexterm significance="normal">
               <primary>table</primary>
               <secondary>filter</secondary>
(Continue reading)

Jan Tosovsky (JIRA | 26 Aug 15:46 2015
Picon

[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=14713440#comment-14713440
] 

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

That white space inside indexterm doesn't seem to be striped by xslt so you had better to avoid it directly in
the source:
<indexterm><primary>table</primary><secondary>customize columns</secondary></indexterm>

> 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}
(Continue reading)

Björn Kautler (JIRA | 26 Aug 15:32 2015
Picon

[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=14713413#comment-14713413
] 

Björn Kautler commented on FOP-2520:
------------------------------------

And there is no space between the indexterms in the source DocBook File. Here the corresponding part:

{noformat}
  <para><indexterm>
      <primary>table</primary>

      <secondary>customize columns</secondary>
    </indexterm><indexterm>
      <primary>customize</primary>

      <secondary>table</secondary>
    </indexterm><indexterm>
      <primary>filter</primary>

      <secondary>table</secondary>
    </indexterm><indexterm>
      <primary>table</primary>

      <secondary>filter</secondary>
    </indexterm>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.</para>
{noformat}
(Continue reading)

Björn Kautler (JIRA | 26 Aug 15:30 2015
Picon

[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=14713410#comment-14713410
] 

Björn Kautler commented on FOP-2520:
------------------------------------

Actually I formatted the code a bit, yes.

Here the original code that is given to FOP:

{noformat}
<fo:block space-before.optimum="0.6em" space-before.minimum="0.4em" space-before.maximum="0.8em">
            <fo:wrapper id="N10119"><!--table, customize columns--></fo:wrapper>
            <fo:wrapper id="N10120"><!--customize, table--></fo:wrapper>
            <fo:wrapper id="N10127"><!--filter, table--></fo:wrapper>
            <fo:wrapper id="N1012E"><!--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>
{noformat}

And here the oritinal code that is given to XEP:

{noformat}
<fo:block space-before.optimum="0.6em" space-before.minimum="0.4em" space-before.maximum="0.8em">
            <fo:wrapper id="N10120" xmlns:rx="http://www.renderx.com/XSL/Extensions" rx:key="table,
customize columns"/>
            <fo:wrapper id="N10127" xmlns:rx="http://www.renderx.com/XSL/Extensions" rx:key="customize, table"/>
            <fo:wrapper id="N1012E" xmlns:rx="http://www.renderx.com/XSL/Extensions" rx:key="filter, table"/>
(Continue reading)


Gmane