Differences calling Saxon8B (outof Oxygen/Java-Application)
Posted: Mon Oct 23, 2006 7:08 pm
Hello,
I try to convert xml to rtf and have problems converting unicode characters to ansi (rtf allows only ansi chars).
For that purpose I have to convert any char above codepoint 255 into its numeric value (string-to-codepoints) and write it (under the rules of rtf) into my target document.
The problem is, when I use Saxon8B out of Oxygen everything works fine, but if I call the same template out of my Java-Application also using Saxon8B, umlauts are not translated correct.
E.g.
With Saxon out of Oxygen Ä remains "Ä" (Decimal code points 196)
With Saxon out of my Application Ä becomes "Ä" (Decimal code points 195 8222)
Are there any 'special' settings or parameters set for the saxon engine in oxygen that could be accountable for that differences?
Any idea? I would be thankful for any suggestion.
I try to convert xml to rtf and have problems converting unicode characters to ansi (rtf allows only ansi chars).
For that purpose I have to convert any char above codepoint 255 into its numeric value (string-to-codepoints) and write it (under the rules of rtf) into my target document.
The problem is, when I use Saxon8B out of Oxygen everything works fine, but if I call the same template out of my Java-Application also using Saxon8B, umlauts are not translated correct.
E.g.
With Saxon out of Oxygen Ä remains "Ä" (Decimal code points 196)
With Saxon out of my Application Ä becomes "Ä" (Decimal code points 195 8222)
Are there any 'special' settings or parameters set for the saxon engine in oxygen that could be accountable for that differences?
Any idea? I would be thankful for any suggestion.