Francis Norton wrote:
...
> I've got to admit that I often sort out these template priority
> questions by testing it then against a good parser, but these two are
> giving me different results!
> 
> Any thoughts as to who's got the spec on their side?
> 

I should add that my workround is to add a priority atribute to the
intruding template, thus:

---
  <!-- and generate "attribute" elements with the rest... -->
  <xsl:template match="itemStatus/*" priority="0">
    <attribute name="{name(.)}"><xsl:value-of
select="text()"/></attribute>
  </xsl:template>
---

which makes both MSXML3 and Saxon behave as if it was Saxon with a
default priority.

My (inexpert) reading of http://www.w3.org/TR/xslt#conflict (section
5.5.2) is that it *should* have a default priority of -0.5, which makes
me think that the problem may be with MSXML3 in this case.

Francis.
-- 
Francis Norton.

Defy Convention? Deify Convention!


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