>First off try UTF-8 instead of utf-8

Xselerator changes it to lowercase, regardless...

Ive read about how MSXML passes strings around which alter your
encoding, but that outputs utf-8 providing you dont specify utf-8 in
xsl:output (?)  Im using saxon anyway.

...I just dont get it.  The xml specifies utf-8, the xsl specifies utf-8
and has xml output type, the output has an xml declaration specifying
utf-8, and its all run through saxon which defaults to utf-8!  So why
does IE 'autodetect' Western European and not recognise   ??



Am I missing something simple here?

cheers
andrew


-----Original Message-----
From: bryan [mailto:bry@xxxxxxxxxx]
Sent: 02 July 2002 18:56
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE:  encoding issues





>Why does msxml4 (when using ie's autoselect) default to unicode without
>the line:

><xsl:output method="xml" encoding="utf-8"/>

>Whereas with it, it defaults to Western European (windows) (iso-8859-1
I
>think) - isnt that the wrong way around?

First off try UTF-8 instead of utf-8
No encoding guru but I wouldn't assume it defaults to iso-8859-1,
microsoft's default encoding for Western European in the rest of windows
should be Windows-1252.
But I would assume that what it would default to would be to ANSI

I think there was something about the Unicode defaulting some time back,
I've noted it as well in the msxsl.exe for the command line.


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





---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.350 / Virus Database: 196 - Release Date: 17/04/2002
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.350 / Virus Database: 196 - Release Date: 17/04/2002
 

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