Just to be complete: >> I wrote >> >> <fo:block font-family=”Arial”/> >> <xsl:text>testowe=12345…ABCD</xsl:text> >> </fo:block> >> >> On PDF his text was splitted into the two lines: >> 12345 >> ABCD
> … 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, … (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: [email protected] For additional commands, e-mail: [email protected]
