Re: CSS Localization

On Thu, Jan 8, 2015 at 7:03 AM, Cameron Jones <cmhjones@gmail.com> wrote:
> Hello www-style,
>
> I'm following up on discussions across html and i18n wgs regarding
> localization of form controls and other locale-specific data:
>
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859
>
> I'd invite you to read through the discussion but i'll also summarize what
> was derived and try to provide some suggestions for what could be a
> localization module for CSS.
>
> ---------------
>
> There is new functionality added within HTML5 which is inherently
> international and requires localization for display to the user. These
> include the new form controls (eg: date, number, etc) and other data
> elements, ie <time> and potentially <data> too.
>
> HTML includes a global "lang" attribute for defining the locale of an
> element using BCP-47 codes, and a method for deriving the applicable locale
> based on an element's parent, meta extension, http header or platform
> locale.
>
> The implementation of localization within browsers uses the platform locale
> for any localization of pages. This leaves no potential for configuring
> localization either to enable a locale override or to enable multilingual
> documents to exist.
>
> It is believed that the place to define the functionality for configuring
> the render locale and any further localization customizations (ie format
> skeletons) should be provided through CSS as a matter of separation of style
> from content.
>
> As such, it is believed that no further changes to HTML are necessary and
> that in order to support the functionality added to HTML5 there is the need
> for additional functionality within CSS.

What's the use-case for overriding the user's platform locale, or
having inputs with different locales on the same page?

~TJ

Received on Friday, 9 January 2015 21:40:27 UTC