- From: <bugzilla@jessica.w3.org>
- Date: Sat, 09 Mar 2013 16:36:10 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859 --- Comment #17 from Addison Phillips <addison@lab126.com> --- (In reply to comment #13) > Well we can't use lang="" itself, since that would break existing pages all > over the Web. How would it break existing content? I don't see a case. > But if the state of the art in describing locales is to use > language codes, then fair enough. Seems a bit weird to me, but whatever. > > > To make progress on this bug, we need the following: > > - CSS-level features for localising content A few features exist for localizing content by language, such as list indicators or via the :lang pseudo operator. But you're correct: it's a gap for html+ css. However presentation of user agent user interface such as calendar pickers or time pickers, whose interface is implementation defined, does not depend on this. > > - A list of what needs to happen with respect to automatic localisation > e.g. <input type=date> UI, <time> rendering... (see also comment 1) This is a job for CLDR, although I imagine getting agreement among browsers will be tricky. > > - A reference to use for locale labels and for how to interpret them when > using them for the things in the previous bullet The ECMAScript I18N extension provides one. It would best if html and JavaScript were identical in regard. > > - Implementor interest Always. But I'm still hoping you will close this bug. I don't want to see an attribute named locale, although I would like see locale/language aware rendering of data in web pages. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Saturday, 9 March 2013 16:36:18 UTC