- From: <bugzilla@jessica.w3.org>
- Date: Wed, 01 Dec 2010 22:26:36 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7202
Anders Berglund <alb.w3c@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alb.w3c@gmail.com
--- Comment #2 from Anders Berglund <alb.w3c@gmail.com> 2010-12-01 22:26:35 UTC ---
The XSL Working Group approved this response at its November 18 2010
Teleconference.
Your comment highlights a number of the difficulties in supporting
the wide variety of conventions used over time in many languages.
Some of these cannot even be represented in a "linear sequence" of
Unicode characters - such as a "titlo" that is "stretched" to cover
all the characters in an old slavic number.
For most of the variations that you list the intention was coverage
by (just before the description of "grouping-separator")
Note:
Implementations may use extension attributes on xsl:number
to provide additional control over the way in which numbers
are formatted.
Do you think this should be augmented and clarified to get the point
across? One could - if you would volunteer to organze a "community"
design effort - add a specific example designed to fully cover a
particular language. I feel that a SINGLE attribute will be too
limiting in the general case so a "standard" @options is probably
not the way to go. The namespace of the extension attributes should
probably clearly identify the language and "authority" of the
definition.
Could you provide examples of where the cardinal form varies based on
e.g. gender? Preferably in more than one language.
--
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 Wednesday, 1 December 2010 22:26:37 UTC