- From: <bugzilla@jessica.w3.org>
- Date: Fri, 30 Jan 2015 21:22:23 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27618
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Michael Kay <mike@saxonica.com> ---
The Working Group discussed this suggestion and did not feel that the use case
was compelling, given the additional complexities of (a) describing a family of
strings to be used for the ten decimal digits, and (b) refining the rules on
things such as grouping positions, which are currently all predicated on each
digit being a single character.
A particular challenge would be defining the rules to ensure that the syntax of
the pattern remains unambiguous. For example, if we allowed the percent,
permille, and exponent separator to be multiple characters, then it would no
longer be sufficient to say they must be different strings, we would need a
rule to ensure that when they appear in a pattern, we can tell which is which.
We also felt that since we are dealing with a computationally complete
language, format-number() is really just a convenience function for handling
common requirements: it doesn't need to do everything imaginable. At some
stage, it becomes easier for users to write their own formatting function.
I'm marking this as resolved, and the XSL WG hopes that I18N will indicate its
agreement by closing the bug. Thank you for your comments.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 January 2015 21:22:24 UTC