[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fop-user
Subject:    Re: character …
From:       "Andreas L. Delmelle" <andreas.delmelle () telenet ! be>
Date:       2011-07-19 18:08:14
Message-ID: D90A4D0A-1A9A-411B-B5C7-67B692637FA0 () telenet ! be
[Download RAW message or body]

Just to be complete:

> > I wrote
> > 
> > <fo:block font-family=”Arial”/>
> > <xsl:text>testowe=12345&#133;ABCD</xsl:text>
> > </fo:block>
> > 
> > On PDF his text was splitted into the two lines:
> > 12345
> > ABCD

> &#133; is the [next line] control character. It should not be used as
> this in FO to PDF.

That is true in this particular context, if you want to avoid the line-break.

However, for all other intents and purposes, &#133; (or the corresponding Unicode \
codepoint U+0085) is a perfectly legitimate typographical aid, and may be used to \
enforce inline linefeeds, independent/regardless of linefeed-treatment="preserve". It \
is defined in UAX#14 as one of a handful of explicit break-characters, and as such, \
is supported by FOP.

There are a few control break-characters which should indeed never be used \
--classical form-feed and line-tabulation-- but those will already cause the XML \
parser to choke, so FOP would never see them.

See also: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/test/layoutengine/standard-testcases/block_uax14_explicit-breaks.xml?view=markup



Regards,

Andreas
---
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]