RE: xsl:number again

Are you suggesting the spec is unclear? It seems clear enough to me:
each number after the first is preceded by the separator token that precedes
the format token used to format it; and if the last token is a
non-aphanumeric one, it gets added at the end. So I don't thing there's any
excuse for a pattern that ends in "1" to produce a number with a "." at the
end. Raise bug reports!

Mike Kay

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Sebastian
> Rahtz
> Sent: 16 October 2001 14:15
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  xsl:number again
>
>
> I have raised this before, but forgot about it until recently.
>
> Consider the input:
>
> <div><div><div><div><div><div></div></div></div></div></div></div>
>
> and the XSLT:
>
>   <xsl:template match="div">
>     <xsl:number level="multiple" format="1.1.1.1.1.1.1"/><xsl:text>
> </xsl:text>
> <xsl:apply-templates/>
>   </xsl:template>
>
> and the result:
>
> 1.
> 1.1.
> 1.1.1.
> 1.1.1.1.
> 1.1.1.1.1.
> 1.1.1.1.1.1
>
> The point being that I cannot reliably suppress the trailing "." on
> numbers. What I want is numbers separated by "." punctuation, but with
> nothing at the end. I *could* use  a choose statement to see how
> deeply nested I am, and use a different format at each level, but
> surely that should not be needed?
>
> Saxon and XT do what I want, Oracle and libxslt don't.
>
> <despair/>
>
> sebastian
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list