Re: [xsl] msxsl encoding bug?

Subject: Re: [xsl] msxsl encoding bug?
From: Bryan Rasmussen <bry@xxxxxxxxxx>
Date: Thu, 31 Mar 2005 19:04:20 +0200
Yeah ANSI is a Microsoft delineation for, IIRC ISO-8859-1, it got the name ANSI
because it was released before the ISO spec was cleared, this may just be lousy
memory here though.  

Anyhow I can't say this with 100% certainty because I didn't have a hex editor
to check the BOM at the beginning of the file, but I did open it in notepad and
try the save as
the save as shows the encoding of the text document you are saving, it has the
possibility of ANSI, Unicode big endian, Unicode, and UTF-8

I'm thinking on reflection what could be happening is the following:

if a file is UTF-8 but without non english characters the BOM is not output,
which is okay because from what I remember from the xml spec a BOM is not
required when a file is UTF-8, Notepad looks at the file, sees no BOM looks at
the character set determines it as ANSI so if I choose save as it tells me it is
ANSI even though if I read it into an XML parser it would read it as UTF-8, the
problem then would be saving it as ANSI if one opened the file and edited it
after generation because I believe a BOM is output at the point of saving. So
probably not a bug after all, but probably a bad decision. 
Bryan Rasmussen

Quoting David Carlisle <davidc@xxxxxxxxx>:

>   and the xml file only has the english character set then the output has an
> xml
>   declaration of utf-8 but the actual content of the document is ANSI
> By ANSI I assume you mean some MS specific code page?
> If the file only has english characters in it then ASCII = UTF8 = most
> Microsoft code pages that extend ASCII.
> So how can you tell that the file is not utf8 encoded?
> 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:
> ________________________________________________________________________

Current Thread