Wierd MSXML3 Behaviour.

Subject: Wierd MSXML3 Behaviour.
From: lists@xxxxxxxxxx
Date: Mon, 2 Oct 2000 20:43:53 +0100
Details:
- July MSXML3.

- XSL Sheet as follows: i.e. identity sheet.

<?xml version="1.0" ?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
  <xsl:output method="xml" encoding="utf-8"/>
  <xsl:template match="/ | @* | node()">
    <xsl:copy>
      <xsl:apply-templates select="@* | node()"/>
    </xsl:copy>
  </xsl:template>
</xsl:stylesheet>

Different results if transformed in different ways. All in ASP. Variable
"renderedXML" was created using the line renderedXML=""

Method 1):
"renderedXML=xmlDOMParam.TransformNode(xslDOMParam.documentElement)"
UTF-16 appears in the resulting XML, but the XML is not displayed in IE5,
IE5 produces the error "Switch from current encoding to specified encoding
not supported."
No matter what encoding I put in the XSL stylesheet, MSXML simply seems to
ignore it and force UTF-16.


Method 2):

"xmlDOMParam.transformNodeToObject xslDOMParam.documentElement, tempXMLDom
renderedXML=tempXMLDom.xml"

In this scenario, IE5 parses the XML quite merrily, but this time, the
resulting XML has no encoding whatsoever, again, MSXML 3 seems to ignore the
UTF encoding, but this way rather than force UTF-16 as in (1), it simply
doesn't put anything there.

Method 3):

"xmlDOMParam.transformNodeToObject xslDOMParam.documentElement, Response".
This works fine, the encoding does appear in the resulting XML whichever
encoding I try (I've only tried UTF-8 or UTF-16).

Has anyone else found this? It seems most bizarre and inconsistent. Has
anyone tried any of these in the September MSXML3?
Someone else must have, I'm trying something so simple.

Roland.



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread