DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8670>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8670 UNICODE/DBCS .FO files (like those produced by XMLSpy) cannot be processed by FOP ------- Additional Comments From [EMAIL PROTECTED] 2002-04-30 21:51 ------- This appears to be a Xerces bug. FOP using xerces-1.2.3.jar distributed with fop-0.20.3 is indeed unable to grok UTF-16 encoded XML. The very same Xerces works with UTF-16 if called by Xalan or with a simple SAX application, which is rather strange. A simple program driving FOP through a JAXP identity transformer fails with Xerces 1.2.3 +Xalan but works if Saxon or Xerces 1.4.4 +Xalan is in the classpath instead. Unfortunately, Xerces 1.4.4 no longer supplies the org.apache.xerces.parsers.SAXParser class necessary for the FOP command line application. As soon as we switch to JAXP, Xerces 1.4.4 or later can be utilized. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
