Hi Folks,

Me again!!

I have a strange problem, relating to yesterday's post. Using the same xml and stylesheets:

Xml file to be transformed:

<rs:data>
    <z:row CarVidNo="33445566" CarRegNo="345rtgy" CarMake="Renault" CarModel="Clio" CarColour="Blue" CarEngine="1.2" CarPrice="5000"/>
    <z:row CarVidNo="55667788" CarRegNo="SXI 6002" CarMake="Vauxhall" CarModel="Corsa" CarColour="White" CarEngine="1.1" CarPrice="1000"/>
</rs:data>

Stylesheets to perform transformations:

<xsl:import href="copy.xslt"/>

    <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" />


      <xsl:template match="*[z:row]">


                <xsl:apply-templates/>

      </xsl:template>


        <xsl:template match="s:Schema">
                <xsl:for-each select="z:row">
                    <xsl:apply-templates />
                </xsl:for-each>
        </xsl:template>


        <xsl:template match="z:row/@*">
          <xsl:element name="{name( )}">
                <xsl:value-of select="." />
          </xsl:element>
        </xsl:template>


        <xsl:template match="z:row">
          <xsl:element name="Cars">
                <xsl:apply-templates select="z:row"/>
          </xsl:element>
        </xsl:template>
</xsl:stylesheet>

And here is the copy stylesheet:

<xsl:template match="node( ) | @*">
  <xsl:copy>
    <xsl:apply-templates select="@* | node( )"/>
  </xsl:copy>
</xsl:template>

However, even though output is specied as UTF-8, the output I am getting is in UTF-16 format.

Out of interest, would this interfer with the way the transformed XML would respond to DOM parsing? I am trying to get info out of the file using DOM and it is falling over when I try to use this code:

psParentNode = pxmlDOM.documentElement.firstChild.childNodes.Item (1).nodeName

I am at a loss to explain this - any ideas?

Cheers,

Morris

>However, even though output is specied as UTF-8, the output I am getting is in UTF-16 format.

This generally means either (a) you are not serializing the result using the XSLT serializer, but using the DOM serializer, or (b) you are serializing the result using the XSLT serializer, but sending the result to a "character" rather than "byte" destination, which means that the final encoding of characters to bytes is not being done by the XSLT serializer. This is all a question of how the transformation is invoked from the API. I've only ever seen this on Microsoft environments, not in Java, because Java doesn't tend to encode output as UTF-16 unless you ask for it explicitly.


Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference