RE: msxml3sp1 & encoding

I'm sorry I wasn't explicit enough.

But your answers helped, not really having clear when the encoding
was beeing done made it a bit difficult to find out what was causing 
the mess.

The trouble was when using xml-spy set to use msxml.dll.
The encoding is set throu the option-menu and the output setting 
in the xsl-file is ignored.

And ... big confusion

The encoding for unkown files was utf-8,
I set the the xsl to output ISO-8859-1,
the Metatag in the output is set to UTF-16
and the display is a mess.

Strange was when using saxon as external ... everything was fine.
(which is the last case you describe)

And when transforming in asp I used to set the response-object to:
Response.ContentType = "text/html; charset=ISO-8859-1"
and everything was fine.
I asume this is the first case you describe before creating the stream
and 
the second is when creating the stream.

To get the Metatag right know I use msxml as external
(xslCommandline-Tool).


 ... And that's it ...

Thanx Philip

| -----Original Message-----
| From: Michael Kay [mailto:mhkay@xxxxxxxxxxxx] 
| Sent: Donnerstag, 26. Juli 2001 19:51
| To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
| Subject: RE:  msxml3sp1 & encoding
| 
| 
| 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
| 
| 

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