This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: xml:output encoding as iso-8859-1 always comes out as UTF-16
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] xml:output encoding as iso-8859-1 always comes out as UTF-16
- From: "Ben Robb" <b dot robb at cscape dot com>
- Date: Fri, 2 Mar 2001 16:45:07 -0000
- Reply-To: xsl-list at lists dot mulberrytech dot com
- Thread-Index: AcCjOAXXCvIBnwZ+S2mhc5GvUaez8wAACPtA
- Thread-Topic: [xsl] xml:output encoding as iso-8859-1 always comes out as UTF-16
the Response object springs to mind...
-----Original Message-----
From: Neil Hunter [mailto:HunterN@rsc.org]
Sent: 02 March 2001 16:28
To: 'xsl-list@lists.mulberrytech.com'
Subject: RE: [xsl] xml:output encoding as iso-8859-1 always comes out as
UTF-16
The reason I wasn't using transformNodeToObject() is that my
transformation
result is not a valid DOM Document. However, I see now that I not
restricted
to a DOM for the result anyway so I'll try some more generic object
instead.
Thanks,
Neil.
> -----Original Message-----
> From: Julian F. Reschke [SMTP:julian.reschke@gmx.de]
> Sent: Friday, March 02, 2001 3:44 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: RE: [xsl] xml:output encoding as iso-8859-1 always
comes
> out as UTF-16
>
> > I get this result loading the XML file (which includes a reference
to
> the
> > stylesheet) into IE5.
> >
> > I get the same result in VB using:
> >
> > myts.Write xmlDOMSource.transformNode(xmlDOMHTMLStyle)
> >
> > where myts is the textstream of a non-Unicode text file.
> >
> > If I am not supposed to be using transformNode then I am not clear,
even
> > >from the SDK documentation, as to what I should use?
>
> transformNodeToObject().
>
>
> 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