Hi,
this was a bug which I just (hopefully) fixed in the CVS. The problem
was that xsl:sort attributes were not interpreted as attribute value
templates.
Tom
PS. Please contact [EMAIL PROTECTED] for CVS access if you don't
have it.
James Eberhardt wrote:
> What I would try is to do some debugging.
>
> <xsl:for-each select="$selectedTable/product">
> <xsl:value-of select="$order" />
> <xsl:sort select="substring(@price,2)" data-type="number"
> order="$order"/>
> </xsl:for-each>
>
> This will output the value of $order. I suspect it is actually wrong. I
> can't see where you are setting it, but you always have to keep in mind the
> scope of variables in XSLT.
>
> Let me know how this goes.
>
> James
>
> -----Original Message-----
> From: Andrew Vorobyov [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 14, 2001 1:50 PM
> To: Sablotron Mailing List
> Subject: RE: [Sab] xsl:sort support
>
> without the curly brackets I have the same result
>
>
