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

[Bug 17859] locale="" attribute

From: <bugzilla@jessica.w3.org>
Date: Tue, 27 Nov 2012 01:28:28 +0000
To: public-i18n-core@w3.org
Message-ID: <bug-17859-3493-2DySEQWv5A@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859

--- Comment #11 from Addison Phillips <addison@lab126.com> ---
(In reply to comment #10)
> (In reply to comment #8)
> 
> > 2012-11-26T15:34:51Z is not a very friendly presentation. I agree that a
> > presentation that is similar to that ("2012-11-26 07:34:51 PST"?) can be
> > useful, removing ambiguity from dates and times, but that usually isn't
> > exactly ISO 8601.
> 
> I agree that for date+time, it's very user-unfriendly. For dates only (, or
> separate dates and times), it can make more sense.

I agree---but I still maintain that this is a format option rather than a
"locale". 

Content authors want/need this kind of control and we *should* be talking about
providing those specific display options for number/date/time/etc.
microformats. 

But I think that @lang is fully sufficient for describing the locale to use...
and that it is desirable to use it for locale.

Put a different way, the locale takes care of knowing that the date separator
is - or slash or dot or what. Some locale might prefer "2012.11.26" to
"2012-11-26". The page author doesn't need to know this when authoring the
page, even if they specify a picture string or skeleton such as:

<input type=date format="y-m-d" value="2012-11-26"> <!-- @lang inherited from
page -->

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 27 November 2012 01:28:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 November 2012 01:28:30 GMT