W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2012

[Bug 17918] i18n-ISSUE-136: Recognition of number formats in Number state

From: <bugzilla@jessica.w3.org>
Date: Wed, 21 Nov 2012 01:59:03 +0000
To: public-i18n-core@w3.org
Message-ID: <bug-17918-3493-Ax1DrZkrBD@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17918

Martin Dürst <duerst@it.aoyama.ac.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |duerst@it.aoyama.ac.jp

--- Comment #7 from Martin Dürst <duerst@it.aoyama.ac.jp> ---
(In reply to comment #4)

> --
> For example, a user agent might support numeric input in the user's local
> format, converting it to the format required for submission as described
> above. This might include handling different grouping or decimal separators
> (such as "12.456,78", as customary in many European locales) or local digit
> shaping (such as the use of digits in Arabic, Persian, Devanagari, Thai, and
> other scripts) or a combination thereof.
> --

Please avoid "local digit shaping". It means displaying ASCII digit codepoints
with totally different glyphs.

The difference between using local digit shapes on display and using the actual
local digit codepoints in the case at hand may be irrelevant because there is
an additional conversion step, but as far as I understand, local digit shaping
is discouraged (it would address just part of localization needs for number
representations anyway).

So please change "local digit shaping  (such as the use of digits in" to "using
local digits  (e.g. digits in".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 21 November 2012 01:59:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 November 2012 01:59:06 GMT