[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
RE: [xsl] IE error | Switch from current encoding to specified encoding not supported.
Subject: RE: [xsl] IE error | Switch from current encoding to specified encoding not supported.
From: "Scott Trenda" <Scott.Trenda@xxxxxxxx>
Date: Wed, 3 Oct 2007 11:34:23 -0500
|
If you're using MSXML, yes! MSXML defaults to UTF-16 whenever you don't
specify <xsl:output encoding="utf-8"/> in your stylesheet.
If that doesn't do it, could you post a sample flow of where your XML is
coming from, and how it's getting to the browser? (including those
stylesheets would help a lot too.)
~ Scott
-----Original Message-----
From: Steve [mailto:subsume@xxxxxxxxx]
Sent: Wednesday, October 03, 2007 11:06 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] IE error | Switch from current encoding to specified
encoding not supported.
Transform is happening server side, so...
<?xml version='1.0' encoding="UTF-8"?>
Would adding
<xsl:output encoding="utf-8"/>
have some additional affect?
-S
On 10/3/07, Scott Trenda <Scott.Trenda@xxxxxxxx> wrote:
> Are you doing this via <?xml-stylesheet?> or via Javascript? I've
> encountered IE misbehaving in UTF-16 with transformToNode() before,
but
> I don't know that I've heard of the same bug happening with a PI.
>
> ~ Scott
>
>
> -----Original Message-----
> From: Steve [mailto:subsume@xxxxxxxxx]
> Sent: Wednesday, October 03, 2007 10:58 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] IE error | Switch from current encoding to
specified
> encoding not supported.
>
> Sure do!
>
> On 10/3/07, Scott Trenda <Scott.Trenda@xxxxxxxx> wrote:
> > Do you have <xsl:output encoding="utf-8"/> at the top of your
> > stylesheet? I know my server-side XSLT processor chokes on UTF-16
> > output.
> >
> > ~ Scott
> >
> > -----Original Message-----
> > From: Steve [mailto:subsume@xxxxxxxxx]
> > Sent: Wednesday, October 03, 2007 10:53 AM
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: [xsl] IE error | Switch from current encoding to specified
> > encoding not supported.
> >
> > I'm confused by this error I am receiving in IE. I've never
> > encountered anything like it and I'm confused as to why the below
> > template would trigger such an error.
> >
> > Strangely, the stylesheet begins with:
> >
> > <?xml version='1.0' encoding="UTF-8"?>
> >
> > not UTF-16 as in the error.
> >
> > ------
> > Error
> >
> > Switch from current encoding to specified encoding not supported.
> > Error processing resource 'https://server.org/private...
> >
> > <?xml version="1.0" encoding="UTF-16"?><i>Not logged in</i>
> > ---------------------------------------^
> >
> > ==========
> >
> > XSL template
> >
> > <xsl:template match="/">
> > <xsl:choose>
> > <xsl:when test="$userID or $noAuth='true'">
> > <xsl:choose>
> > <xsl:when test="$Mode='index'">
> > <xsl:apply-templates
> select="/"
> > mode="index" />
> > </xsl:when>
> > <xsl:when test="$Mode='search'">
> > <xsl:choose>
> > <xsl:when test="$R">
> >
> > <xsl:apply-templates select="/" mode="search" />
> > </xsl:when>
> > <xsl:otherwise>
> > <h2>No
> > results</h2>
> > </xsl:otherwise>
> > </xsl:choose>
> > </xsl:when>
> > <xsl:when test="$Mode='report'">
> > <xsl:apply-templates
> select="/"
> > mode="report" />
> > </xsl:when>
> > <xsl:otherwise>
> > <xsl:call-template
> > name="warning" />
> > <xsl:apply-templates />
> > <xsl:call-template
> > name="warning" />
> > </xsl:otherwise>
> > </xsl:choose>
> > </xsl:when>
> > <xsl:otherwise>
> > <i>Not logged in</i>
> > </xsl:otherwise>
> > </xsl:choose>
> > </xsl:template>
Current Thread |
- RE: [xsl] IE error | Switch from current encoding to specified encoding not supported., (continued)
- Scott Trenda - Wed, 3 Oct 2007 10:56:16 -0500
- Steve - Wed, 3 Oct 2007 11:58:06 -0400
- Scott Trenda - Wed, 3 Oct 2007 11:02:17 -0500
- Steve - Wed, 3 Oct 2007 12:06:00 -0400
- Scott Trenda - Wed, 3 Oct 2007 11:34:23 -0500 <=
- Steve - Wed, 3 Oct 2007 12:50:22 -0400
- W Charlton - Wed, 3 Oct 2007 17:24:13 +0100
- Steve - Wed, 3 Oct 2007 12:30:25 -0400
- W Charlton - Wed, 3 Oct 2007 17:49:31 +0100
|