You need to be clear (a) which software is doing the serialization, and (b)
which software is doing the character encoding.

If you write the transformation output to a DOM, then the XSLT processor is
doing neither, and the serialization can't be affected by xsl:output.

If you write to a character stream, the XSLT processor is serializing but
the character encoding is being done by the operating system.

If you write to a byte stream, the XSLT processor is doing both serializing
and encoding.

Mike Kay
Software AG

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of
> Philip Rangel
> Sent: 26 July 2001 18:24
> To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  msxml3sp1 & encoding
>
>
> I read dave pawson's faq and the one 4xt,
> but didn't find the right answer.
>
> althogh i set the xsl-output-method to Latin one:
> <xsl:output method="html" encoding="iso-8859-1" indent="yes"/>
>
> I get
>
> <META http-equiv="Content-Type" content="text/html; charset=UTF-16">
>
> I'm using msxml3 with the msxml3sp1.
>
> Is there a wy to fix this ?
>
> Btw the explanation on special-character's was very interesting,
> but I missed utf-16.
>
>
> ---------------------------------------------------------------------
> Philip Rangel                           mailto:pr@xxxxxxxxx
> Projektleiter                           fon: +49 040-890 69 674
> ---------------------------------------------------------------------
> Engine GmbH & Co KG                     http://www.engine.de
> Stresemannstrasse 374b                  fon: +49 040-890 69 660
> 22761 Hamburg                           fax: +49 040-890 69 690
> ---------------------------------------------------------------------
> Im Netzwerk der Tinfactory              http://www.tinfactory.de
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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