Re: IE error

[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: IE error | Switch from current encoding to specifi

Subject: Re: IE error | Switch from current encoding to specified encoding not supported.
From: Steve <subsume@xxxxxxxxx>
Date: Wed, 3 Oct 2007 12:50:22 -0400
Re:  IE error | Switch from current encoding to specifi
I've included <xsl:output encoding="utf-8"/> into all of my
stylesheets and nothing has changed.

my ASP processor scripts use a class which builds XML based on some
session data and then transforms local.xsl, which imports master.xsl
(both of which have <xsl:output encoding="utf-8"/>).

You want to know more about the construction of the XML?

Its getting to the browser via the transform method of an xslt ASP object.

-Steve

On 10/3/07, Scott Trenda <Scott.Trenda@xxxxxxxx> wrote:
> 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:  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:  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:  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

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.