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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Nov 2012 01:34:07 +0000
To: public-i18n-core@w3.org
Message-ID: <bug-16165-3493-apZ24WG8EJ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16165

--- Comment #3 from Norbert Lindenberg <w3-bugs@norbertlindenberg.com> ---
Discussed at the Internationalization WG meeting 2012-11-01: What's really
causing the confusion is the phrase "User agents must not allow the user to set
the value...". 

If we understand the intent of the spec correctly, the user doesn't set the
value at all; instead, the user types a string in a localized format, it gets
interpreted and converted to a value, using algorithms that are not specified
in HTML. The conversion algorithms discussed in the spec have nothing to do
with user input; they handle text that's part of the HTML source or form
submissions.

The phrase above contradicts this intent and should be fixed.

In addition, the note in the section uses a somewhat extreme example (Persian
or Arabic numbers), so it's not obvious that more subtle differences also need
to be handled, such as different decimal and grouping separators for German or
for India.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 20 November 2012 01:34:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 November 2012 01:34:09 GMT