Well, just for the record, i solve my problem, by using
<xsl:variable name="snode" select="(//Menu)[position()=$pos]"/>
instead of
<xsl:variable name="snode" select="(//Menu)[$pos]"/>
A million neurones i burn to reach this solution!!!
This seems clearly a bug in XSLTProcessor, does anyone knows where can
i submit this?
Did you show us the declaration of the variable $pos? If it's a string or a
result tree fragment, then the two expressions are not equivalent. They are
only equivalent if it is a number. There is a note in the XSLT 1.0
specification warning you of this.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--