Subject: RE: More wierdbehaviour. From: Andrew Kimball <akimball@xxxxxxxxxxxxx> Date: Mon, 2 Oct 2000 16:56:33 -0700 |
The encoding of your .xsl file is declared to be "UTF-16" in your xmldecl. This means that the .xsl file must be saved as Unicode (I usually use Notepad under Windows 2000 to do this). If you've saved it as a regular ASCII file, your declared encoding will not match the actual encoding. You need to check the msxmlDomParam.parseError.reason when you load. If you do, I'll bet you'll see this error: "Switch from current encoding to specified encoding not supported.". When there is a parse error, the document will consist of a single root node, so the .XML property will return the empty string. ~Andy Kimball MSXSL Dev -----Original Message----- From: lists@xxxxxxxxxx [mailto:lists@xxxxxxxxxx] Sent: Monday, October 02, 2000 3:23 PM To: xsl-list-digest@xxxxxxxxxxxxxxxx Cc: lists@xxxxxxxxxx Subject: More wierdbehaviour. All in MSXML 3 July edition: 1) Take the following identity XSL. <?xml version="1.0" encoding="UTF-16" ?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" encoding="UTF-16"/> <xsl:template match="/ | @* | node()"> <xsl:copy> <xsl:apply-templates select="@* | node()"/> </xsl:copy> </xsl:template> </xsl:stylesheet> Load it into a DOM like so: msxmlDomParam.Load(Server.MapPath(localFile)) msxmlDomParamXML=msxmlDomParam.xml msxmlDomParamXML will now equal "" i.e. have no value. 2) Change the encoding, so that it is now UTF-8. And "msxmlDomParamXML" will now be the XSL style sheet. Doesn't this strike you as rather odd? Roland. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
More wierdbehaviour., lists | Thread | xsl structuring...., Saif Khaja |
RE: Wierd MSXML3 Behaviour., Andrew Kimball | Date | RE: xsl structuring...., Ben Robb |
Month |