This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

microsoft latest, bug with extension elements?


In a test file, I say

<xsl:variable name="processor">
  <xsl:value-of select="system-property('xsl:vendor')"/>
</xsl:variable>

<xsl:choose>
 <xsl:when test="contains($processor,'Clark')">
  <xt:document href="{$filename}">
   <xsl:call-template name="writestone"/>
  </xt:document>
 </xsl:when>

...
 <xsl:otherwise>
   <xsl:message>No support for multiple output files </xsl:message>
   <xsl:call-template name="writestone"/>
 </xsl:otherwise>
</xsl:choose>

but when I run the MSXML processor, it says "Attribute href is invalid 
on xt:document" (or the like). Can anyone see how the processor gets
into the XT <when> statement? or is it when parsing the XSL
stylesheet?


also, I find that when output method is text, the following

<xsl:template name="Show">
<xsl:value-of select="name()"/>
<xsl:text> </xsl:text>
<xsl:value-of select="generate-id()"/>
<xsl:text>
</xsl:text>
</xsl:template>

does not generate a new line, just a space. surely wrong?

is there some easy way to report bugs to Microsoft?

Sebastian


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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]