W3C home > Mailing lists > Public > xsl-editors@w3.org > April to June 2000

Re: xsl:number Recomendation

From: James Clark <jjc@jclark.com>
Date: Mon, 26 Jun 2000 13:44:21 +0700
Message-ID: <3956FBC5.19109EA3@jclark.com>
To: Michael Holder <holderm@tusc.com>
CC: xsl-editors@w3.org
If you don't want thousand separators, then all you have to do is not
specify a grouping-separator attribute.

> Michael Holder wrote:
> 
> I think it would be a good idea if the next recomendation specified
> how to handel a special case for the xsl:number attributes
> grouping-separator and grouping-size.
> 
> In my application I wanted to produce numbers that are integers with
> no separator character (so that thousands would not be separated by a
> comma for example).  In order to do this I had to set
> grouping-separator=" " and grouping-size="10000" which will be
> sufficient for very lagre integers; much larger than the application
> will ever encounter.  However I think it would be better if
> grouping-separator="" (a null string) were sepcifically allowed as a
> means of turning "commas" off.  The xalan parser for example
> (www.xml.apache.org/) gives a lot of java exceptions and can't handle
> it.  Also, if grouping-size="0" were specified to mean that "commas"
> or whatever were turned off that would be another good way to do it (I
> would allow both methods).
> 
> Since the values for grouping-separator and grouping-size could be a
> data driven parameter into a template or stylesheet it would be a good
> idea to make it a bit more robust for this kind of situation.
> 
> I hope this idea was helpful and please let me know what you think of
> it. I look forward to hearing from you.
> 
> - Mike
Received on Monday, 26 June 2000 02:53:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:50 GMT