otherwise <xsl:number/> was producing ""
T the count attribute will make a difference if the current node isn't
an fm:DATA. You don't say what the current node is, the XSLT 1 spec was
a little fuzzy (to say the least) on edge cases of xsl:number whether it
should produce 0 or "" or 1 or ... (partly because it referenced a java
spec that then changed) XSLT2's specification of xsl:number is much more
precise and self contained.
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--