[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Loosing encoding information
> > '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) One final tidbit : in case this wasn't clear yet, you'll want to make sure that your stylesheet contains the following element : <xsl:output method="html" encoding="iso-8859-1" /> Otherwise the output will be UTF-8 encoded and that won't make your browser happy (since the HTTP headers tell it to expect iso-8859-1). Or you could alter Response.Charset to say UTF-8. 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
|