RE: SAXON and UTF-8

Fact is:

- the XML spec has UTF-8 with BOM as *example* in appendix F.

- Notepad in Windows 2000 can save as UTF-8, and *will* add the BOM.

I don't say I like this, but it's not a matter of personal preferences,
right?

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of XML
> Everywhere
> Sent: Thursday, September 27, 2001 7:04 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  SAXON and UTF-8
>
>
> Yes.. AFAIK, the BOM is for UTF-16 files,
> not UTF-8.  That is based on my coding
> experience with the default 16-bit
> UNICODE support on Windows NT
> and 2000.
>
> I think notepad supports UTF-16,
> not UTF-8, unless you have a special international
> version of Windows installed.  The tools for
> SQL server behave similarly.
>
> ----- Original Message -----
> From: "Michael Kay" <mhkay@xxxxxxxxxxxx>
> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, September 27, 2001 9:27 AM
> Subject: RE:  SAXON and UTF-8
>
>
> > Windows Notepad saves UTF8 files with Byte Order Mark, and
> > AFAIK, the XML
> > parser in Saxon (AElfred) doesn't support this (at least it
> > didn't last time I checked).
> >
>
> The question is, can an XML document (or entity) in UTF-8 encoding start
> with a BOM? The fact that Unicode allows it, and the fact that Notepad can
> create it, doesn't make it legal XML.
>
> My reading of the XML spec is that it expects to find BOM only in UTF-16
> files. I can't see any total prohibition of a BOM in a UTF-8 file, but the
> spec certainly seems to assume that they won't occur. If anyone thinks
> otherwise, I'd like to see evidence from the XML specification,
> which is the
> only definitive source.
>
> This is of course totally off-topic for XSLT.
>
> Mike Kay
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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