It turns out that this was reported before - see the archive at

Apparently, this is a bug in FOP 0.20.4 but I have been successful
in creating a workaround - I used a font editor (like pfaedit) to
'hi-jack' an existing unicode character that I don't expect ever
to use (in my case, 1488 - a Hebrew character) and turned it into
a tiny new character.  Then I replaced all no-break spaces with the
new character in my fo file.  FOP is able to render the new character
correctly but, because is is not visible under a zoom of less than
800%, it appears as a space!

A bit of a round-the-houses solution but effective - at least until
this strange bug is fixed.

-----Original Message-----
From: Doherty, Michael [mailto:[EMAIL PROTECTED]
Sent: 04 November 2002 12:53
Subject: no-break space in unicode font

I am producing pdfs that contain Japanese characters (among others).
Accordingly, I have created a font xml file from osaka.unicode.ttf to embed
in the pdf files.  This works (ie produces Japanese characters) but now I
find that no-break space characters (unicode 160 decimal; 00A0 in hex) are
not correctly handled.  I usually get the 'unkown' unicode character in
their place (a square outline) but sometimes get other, apparently unrelated

Has anybody else experienced something similar?  Are there any known
solutions?  Can the font be manipulated to solve the problem?

Any ideas would be greatly appreciated.

Many thanks,

This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.

Reply via email to