Subject: Re: [xsl] Encoding problem From: David Carlisle <davidc@xxxxxxxxx> Date: Wed, 31 Aug 2005 12:15:48 +0100 |
> I opened the file using UltraEdit. The sequence shows > as 94 for the trouble character. presumably that means hex 94. this (as a single byte) isn't the utf8 encoding of anything. So if your encoding declaration specifies utf8 (and this is not being overridden/corrected by a higher level proptocl such as an http mime type) then your file is not well formed and should be rejected with a fatal error. If your file is latin-1 encododed (iso-8859-1) <?xml version="1.0" encoding="iso-8859-1"?> then byte hex 94 will represent the unicode character hex 94 (decimal 148) which is <description unicode="control">CANCEL CHARACTER</description> which is legal but probably not what you want. So probably you are using a microsoft-specific encoding such as cp1252 http://en.wikipedia.org/wiki/Windows-1252 which does indeed say that hex 94 is a double quote. So you could use (if your parser supports this encoding) <?xml version="1.0" encoding="cp1252"?> But better would be to generate your source file in a standard encoding such as utf8, if that is possible. David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Encoding problem, amita rathore | Thread | RE: [xsl] Encoding problem, Michael Kay |
RE: [xsl] Encoding problem, amita rathore | Date | RE: [xsl] Encoding problem, Michael Kay |
Month |