|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Encoding problem or what else?
----- Original Message ----- From: "George Cristian Bina" <george@xxxxxxxxxxxxx> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Sent: Thursday, December 08, 2005 09:16 Subject: Re: Encoding problem or what else? > Hi, > > Xerces handles the UTF-8 BOM correctly since many years now. What you > need to check is how you create the input source for the XML that you > pass to the transformation. If you pass only the system ID then Xerces > will escape automatically the BOM if the encoding is UTF-8. If you pass > a Reader to the parser then it is your task to skip the UTF-8 BOM. IIRC > there is a bug on Sun bugzilla that says that the InputStreamReader does > not skip the UTF-8 BOM when you give it a UTF-8 byte stream. > > Now the error message: "Document root element is missing." seems > different than what Xerces gives if you enter a character before the XML > header: "The processing instruction target matching "[xX][mM][lL]" is > not allowed." so it is possible that you are using some other XML parser. > > Hope that helps, > George > --------------------------------------------------------------------- > George Cristian Bina > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > Yes, as Micheal explained JDK 1.4.2 is using the "crimson" parser. Now my problem is to understand how to replace this with xerces. Thanks! Bye, Flavio
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








