-----Original Message-----
From: "Jack Cane" <jwcane(_at_)enw-ltd(_dot_)com>
<xsl:template match="etd:xRef">
<xsl:value-of select="@etd:refElemType"/>
<xsl:text> </xsl:text>
<xsl:value-of select="key('kEqn', '@etd:refElemID')"/>
<xsl:text> </xsl:text>
<xsl:value-of select="xsl:number[(_at_)Target='etd:refElemID']" />
<xsl:value-of select="xsl:number[(_at_)Target=etd:refElemID]"/>
</xsl:template>
Now you've got my head spinning.
1) Please show an "etd:xRef" element which is processed by this template and
show the output the template produces.
2) Please show the output you would like the template to produce.
3) What is the purpose of the <xsl:text> </xsl:text> element?
4) These are way wrong:
<xsl:value-of select="xsl:number[(_at_)Target='etd:refElemID']" />
<xsl:value-of select="xsl:number[(_at_)Target=etd:refElemID]"/>
<xsl:number> can take zero to nine attributes, and none of them is "select" or
anything remotely related to it. That is why we must see the proposed input and
proposed output along with the proposed template. This kind of help is a
three-legged stool. It can't stand up if one of the legs is missing!
--
Charles Knell
cknell(_at_)onebox(_dot_)com - email
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list