Subject: RE: [xsl] msxml3sp1 & encoding From: "Julian Reschke" <julian.reschke@xxxxxx> Date: Thu, 26 Jul 2001 19:37:48 +0200 |
FAQ. You use MSXML and obtain the result of the transformation as COM string. COM strings are always encoded in UTF-16. You need to use a different interface, for instance transformNodeToObject. jr > -----Original Message----- > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Philip Rangel > Sent: Thursday, July 26, 2001 7:24 PM > To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx > Subject: [xsl] 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] msxml3sp1 & encoding, Philip Rangel | Thread | RE: [xsl] msxml3sp1 & encoding, Michael Kay |
[xsl] msxml3sp1 & encoding, Philip Rangel | Date | RE: [xsl] msxml3sp1 & encoding, Michael Kay |
Month |