This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Loosing encoding information
- From: "Jonathan Perret" <jonathan at holylabs dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 20 Feb 2002 17:05:54 +0100
- Subject: Re: [xsl] Loosing encoding information
- References: <F148L1c00goZolmRBaY0000f9d9@hotmail.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
> Jonathan Perret:
> 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))
> %>
> 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...?
Yes it's enough, apart from the fact that the method is called
transformNodeToObject() :
oXml.transformNodeToObject(oXSL,Response)
You can think of it as having transformNodeToObject call
Response.Write internally (it doesn't actually use the
Write method but you get the idea).
Do look up transformNodeToObject in MSDN, it will tell you all you
need to know.
Cheers,
--Jonathan
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list