Thank you sir,

I was thinking to the output way because opening for instance a PS output I had in a full text the character # that's why I was thinking to a problem for encoding unicode, but indeed PDF is half text and half binary.

Best regards,

A.Brillant


J.Pietschmann wrote:

JAPISoft wrote:

I transform a .FO to a PDF but this .FO contains Eastern european characters (ISO-8859-2/UTF-8 compatible), when looking at the resulting PDF I have
a '#' for each eastern character.

[...]

This is as if the PDF font was ignoring my eastern characters. But I feel the problem is in the output way, because eastern european characters may require two encoding bytes.


Your feeling isn't quite correct. Check the FAQ:
 http://xmlgraphics.apache.org/fop/faq.html#pdf-characters

When using the (org.apache.fop.apps) Driver class, I have noticed that the output must be an OutputStream, so this is not character compatible but byte only compatible, it seems unicode cannot be processed correctly ?



PDF isn't text, it is a binary format. For details, check the PDF spec.

J.Pietschmann


.


Reply via email to