[Bug 17859] Mechanism to enable localisation of form controls and other locale-specific data

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|locale="" attribute         |Mechanism to enable
                   |                            |localisation of form
                   |                            |controls and other
                   |                            |locale-specific data

--- Comment #20 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Say you have a page that says:

   <body lang="en-US">
     <p>Enter your date: <input type=date></p>
   </body>

...and you view it today in a UK setting. You'll geta UK widget. If we change
the widget based on the lang="" attribute, the page will change behaviour, in a
way that the author never expected nor tested for. Given the prevalence of
copy-paste authoring, it's extremely likely that there'll be many pages with
this kind of thing going on. It's bad form to take something that previously
had no effect, and make it have an effect of changing the user's interface.

(In reply to Addison Phillips from comment #17)
> > 
> > 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.

If we're going to do this, we should do it right. Otherwise, we'll have to
introduce more and more hooks so that we don't break pages each time.


> >  - 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.

I mean that we need a list of HTML features that we want localised, and rules
for how to apply the CLDR information to each one.


> >  - 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.

URL?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 23 October 2013 20:39:39 UTC