- From: <bugzilla@jessica.w3.org>
- Date: Sun, 25 Nov 2012 17:56:07 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859 --- Comment #3 from Addison Phillips <addison@lab126.com> --- I strongly oppose adding a locale attribute to HTML. The @lang attribute already contains the necessary information and could solve the vast majority of formatting problems. Having a separate attribute would be confusing. In the recent discussion of calendars, Richard pointed out the problem of tagging the language of other attributes that are different from the body of the page or the desired format. This is a legitimate issue--but generally rare and one we have not solved for other text properties like direction either. To answer your question, CLDR does define formats and the mapping for locale subtags that extend language tags (RFC6067 makes these valid in language tags). Some vendors will probably object to making CLDR normative for formats. As with the ECMAScript I18N extension, this isnt a barrier to what HTML needs to do though. So... I would prefer if this bug were just closed. The right way to address this in my opinion would be by adding normative text about formatting or displaying values according to language (locale) of the element as described by @lang. i.e. this : <input type=number value=123456.78 lang=de-CH> might display as something like this: [ 123'456,78] -- You are receiving this mail because: You are on the CC list for the bug.
Received on Sunday, 25 November 2012 17:56:12 UTC