W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2013

[Bug 21599] format-number() integer-part grouping overly prescriptive

From: <bugzilla@jessica.w3.org>
Date: Sat, 06 Apr 2013 19:32:08 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-21599-523-JMJkscudD3@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21599

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
When the specification describes things by means of an algorithm, there is no
requirement for an implementation to use the same algorithm; it can use any
algorithm it likes that delivers the same result.

The format-number text is the result of a great deal of review and feedback
during the course of many drafts of the XSLT 2.0 specification, resulting from
experience with XSLT 1.0 where different implementors interpreted the
specification differently. If it seems to spell things out in too much detail,
that's a reaction against the 1.0 spec which left things far too vague. I'm
very reluctant to make any changes motivated only by making it simpler or less
algorithmic, because there's too much risk of introducing an accidental
incompatibility or ambiguity.

The grouping positions on the fractional side do not need to be extrapolated
because there will never be more digits in the result than there are in the
picture.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 6 April 2013 19:32:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:52 UTC