On 5/20/05, David Carlisle <davidc(_at_)nag(_dot_)co(_dot_)uk> wrote:
Any suggestions?
Wendell explained that in the message that you quoted.
<xsl:function name="bib:footcite" as="xs:string">
<xsl:param name="footciteable" as="element()"/>
<xsl:number level="any" select="$footciteable"/>
</xsl:function>
he said
In a function, I believe this means passing in your context node as a
parameter and changing context to it explicitly before invoking xsl:number.
Apart from that (note this is different from a named template, which keeps
the context from which it's called), I don't see why it shouldn't work. And
it's easy enough to test.
Well I'm obviously not understanding something about context switching
here then, because this yields the same result as my previous example:
<xsl:function name="bib:footcite" as="xs:string">
<xsl:param name="footciteable" as="element()"/>
<xsl:for-each select="$footciteable">
<xsl:number level="any" select="."/>
</xsl:for-each>
</xsl:function>
Bruce
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--