[Home] [By Thread] [By Date] [Recent Entries]

Subject: RE: Encoding issue
From: "Julian Reschke" <julian.reschke@xxxxxx>
Date: Wed, 15 Aug 2001 10:13:51 +0200
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Mike Brown
> Sent: Wednesday, August 15, 2001 2:04 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  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


Current Thread
  • Encoding issue
    • Jason Macki - Mon, 13 Aug 2001 17:34:46 -0400 (EDT)
      • Mike Brown - Tue, 14 Aug 2001 00:32:24 -0400 (EDT)
      • <Possible follow-ups>
      • Jason Macki - Tue, 14 Aug 2001 12:20:25 -0400 (EDT)
        • Mike Brown - Tue, 14 Aug 2001 20:13:03 -0400 (EDT)
          • Julian Reschke - Wed, 15 Aug 2001 04:23:04 -0400 (EDT) <=
          • Michael Beddow - Wed, 15 Aug 2001 06:04:10 -0400 (EDT)
          • Mike Brown - Wed, 15 Aug 2001 14:38:20 -0400 (EDT)
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member