Altova Mailing List Archives


RE: [xsl] Microsoft.XMLDOM UTF-8 Encoding!

From: "Julian Reschke" <julian.reschke@------>
To:
Date: 7/11/2003 10:43:00 PM
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Rob Rohan
> Sent: Saturday, July 12, 2003 12:30 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] Microsoft.XMLDOM UTF-8 Encoding!
> 
> 
> I am going way out here, so please swat me down if I am wrong. If I
> remember correctly the first byte of a file will tell if it is (really)
> utf-8 or iso-8859-1 encoded. You can say its utf-8 in the declaration,

Wrong.

> but if the file is saved with an editor that is only capable of saving
> in iso-8859-1 format, the first byte of the file will say so (something
> about bit order I believe). What you could be running into is a file

No. The BOM (Byte Order Mark) is *optional* in UTF-8.

> that truly is iso-8859-1 (or utf-16 etc) encoded saying its utf-8 - and
> whatever process you are using to read the xml file doesn't buy what you
> are saying.

Correct.

> ...

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.