[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Loosing encoding information
> 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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|