W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2010

[Bug 10387] [FO11]: format-integer format token to disallow digits besides 0 or 1

From: <bugzilla@jessica.w3.org>
Date: Fri, 20 Aug 2010 18:39:46 +0000
To: public-qt-comments@w3.org
Message-Id: <E1OmWVG-00032S-3t@jessica.w3.org>

--- Comment #5 from Michael Kay <mike@saxonica.com>  2010-08-20 18:39:45 ---
The text for this function has in fact been significantly improved since the
Dec 2009 working draft.  

The paragraph cited in comment #0 now reads: "a mandatory-digit-sign is a
Unicode character in category Nd. All mandatory-digit-signs within the format
token must be from the same digit family, where a digit family is a sequence of
ten consecutive Unicode characters in category Nd, having digit values 0
through 9. Within the format token, these digits are interchangeable: a
three-digit number may thus be indicated equivalently by 000, 001, or 999." -
which seems to address the point you are making.

I'm not sure I understand the problem you are describing in comment #2. This
text has been part of the xsl:number specification for many years. By saying
"Any other format token", it means an alphanumeric not listed above, for
example greek letter alpha, and indicates that if the implementation supports
it, this format token may be used to denote a numbering sequence such as
&#945;, &#946;, &#947;, ... The first rule (or two rules, in the Dec 2009
version) covers format tokens containing Unicode digits; the subsequent rules
therefore are only concerned with tokens made up of non-digits.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 20 August 2010 18:39:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:32 UTC