This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Encoding issue
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Encoding issue
- From: "Julian Reschke" <julian dot reschke at gmx dot de>
- Date: Wed, 15 Aug 2001 10:13:51 +0200
- Reply-To: xsl-list at lists dot mulberrytech dot com
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Mike Brown
> Sent: Wednesday, August 15, 2001 2:04 AM
> To: xsl-list@lists.mulberrytech.com
> Subject: Re: [xsl] Encoding issue
>
>
> Jason Macki wrote:
> > I was able to solve the problem by changing the encoding of the source
> > document, and the encoding of the output element of the stylesheet to
> > utf-16.
>
> Can you post what you did? (code-wise)
>
> This question comes up every couple of months on the list, but
> I haven't seen any clear explanations of exactly when MSXML produces
> UTF-16 and when not...
It does this when you obtain an XML serializiation in the form of a COM
string, for instance using the .xml property or transformNode() (this is
also documented in the MSXML SDK I think).
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list