This is the mail archive of the
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:10:23 +0100
- Subject: Re: [xsl] Loosing encoding information
- References: <JIEGINCHMLABHJBIGKBCEECHEBAA.firstname.lastname@example.org>
- Reply-to: xsl-list at lists dot mulberrytech dot com
> > '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
Or you could alter Response.Charset to say UTF-8.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list