xsl-list
[Top] [All Lists]

RE: [xsl] IE error | Switch from current encoding to specified encoding not supported.

2007-10-03 09:34:52
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(_at_)gmail(_dot_)com] 
Sent: Wednesday, October 03, 2007 11:06 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
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(_dot_)Trenda(_at_)oati(_dot_)net> 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(_at_)gmail(_dot_)com]
Sent: Wednesday, October 03, 2007 10:58 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] IE error | Switch from current encoding to
specified
encoding not supported.

Sure do!

On 10/3/07, Scott Trenda <Scott(_dot_)Trenda(_at_)oati(_dot_)net> 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(_at_)gmail(_dot_)com]
Sent: Wednesday, October 03, 2007 10:53 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
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>


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--

<Prev in Thread] Current Thread [Next in Thread>