As far as I know, zero-width spaces are widely used with 0.20.5. The next FOP release will also support zero-width spaces (0.91beta doesn't).
That said, I think you should have a look at the XSL-FO files you generate from your properties files. You can then backtrack from there to find out why the zero-width spaces don't work, or rather why not the right characters are generated/used. The problem is either the character used by your translators or by your converter. Good luck. On 21.03.2006 17:57:41 Fabrizio Caldas wrote: > I'm using the embedded FOP version 0.20.5 to create PDFs. > The text of the PDF comes from properties files. > These properties files are in many different languages. > Only Chinese and Japanese have overflowing characters. > > I've asked the translators to insert "zero width spaces" in Unicode. > All the properties file are UTF-8 encoded. > They tried inserting zero width spaces as they know how, but up to now > it doesn't seem to work. > > Has any one ever tried to insert zero width spaces into a properties > file and use it to create a PDFs? > > I'm trying to find a way to recognize the zero width space that they > insert in the properties file or maybe replace whichever characters > they insert as a &200B. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
