This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Loosing encoding information
- From: "Julian Reschke" <julian dot reschke at gmx dot de>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 20 Feb 2002 17:03:53 +0100
- Subject: RE: [xsl] Loosing encoding information
- 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 Ragulf
> Pickaxe
> Sent: Wednesday, February 20, 2002 4:31 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: Re: [xsl] Loosing encoding information
>
>
> Hello (yet) again :)
>
> Jonathan Perret:
> >Julian certainly meant the transformNodeToObject method.
> <SNIP>
> >I don't know if you can use transformNodeToObject on the client though.
>
> I am sorry if I confused the issue writing "(on the client)"
> which was where
> I took the example from. The code in "on the server" in w3schools.com's
> website is the same <% ..
> 'Transform the file
> Response.Write(xml.transformNode(xsl))
That's exactly what you shouldn't do.
> %>
> I am transforming serverside, but I don't know the use of
> transformNode(a, b) at all. I presume from the examples that output is
> contained in b? Or does b tell the style of the output.
> Surely it is not enough to write:
> ..
> oXml.transformNode(oXSL, response) %>
> and expect the output to be shown in the homepage...?
No, it's
oXml.transformNodeToObject(oXSL, response)
(my typo, sorry).
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list