On Oct 31, 2005, at 22:18, Andreas L Delmelle wrote:
On Oct 27, 2005, at 06:29, Manuel Mall wrote:
Actually something like:
fo:block background-color=yellowword1fo:character
character=#10;/fo:character character=
/word2fo:character character= /word3fo:character
character=#10;//fo:block
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37318.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Currently if one puts a zero-width-space (U+200B) into an XSL-FO file
(or specifies linefeed-treatment=treat-as-zero-width-space) it is
rendered as a missing character in PDF. Is that correct, i.e. does
this character have to exist in the font used or should the formatter
or renderer simply
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37318.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Manuel Mall wrote:
Currently if one puts a zero-width-space (U+200B) into an XSL-FO file
(or specifies linefeed-treatment=treat-as-zero-width-space) it is
rendered as a missing character in PDF. Is that correct, i.e. does
this character have to exist in the font used or should the formatter
On Nov 1, 2005, at 15:52, Manuel Mall wrote:
Currently if one puts a zero-width-space (U+200B) into an XSL-FO file
(or specifies linefeed-treatment=treat-as-zero-width-space) it is
rendered as a missing character in PDF. Is that correct, i.e. does
this character have to exist in the font used
On Nov 1, 2005, at 10:04, Manuel Mall wrote:
I am sure it is doable - but is it worth it at this stage? Possibly
after a better understanding of the white-space handling issues that
whole current system needs revision? One problem with the current char
iterator is that it iterates over inline
On Tue, Nov 01, 2005 at 11:40:42PM +0800, Manuel Mall wrote:
This is probably a question for Luca or Simon.
In LineLM we have this code:
// ignore KnuthGlue and KnuthPenalty objects
// at the beginning of the line
seqIterator =
On Mon, Oct 31, 2005 at 03:25:12PM +0800, Manuel Mall wrote:
In a previous post Joerg pointed to the Unicode Standard Annex #14 on
Line Breaking (http://www.unicode.org/reports/tr14/) and his initial
implementation: http://people.apache.org/~pietsch/linebreak.tar.gz.
I had since a closer
Simon Pepping wrote:
Is our current hyphenation method a subset of Unicode's method?
Umm. What's the relation between hyphenation and TR14 (except for
handling soft hyphens)? I guess you confuse finding line breaks
in general and line breaking due to hyphenation.
I seem to recall that the
On Wed, 2 Nov 2005 01:03 am, Chris Bowditch wrote:
Manuel Mall wrote:
Currently if one puts a zero-width-space (U+200B) into an XSL-FO
file (or specifies linefeed-treatment=treat-as-zero-width-space)
it is rendered as a missing character in PDF. Is that correct,
i.e. does this character
11 matches
Mail list logo