Time zones: the localized GMT formats

[Shervin Afshar]

On Sat, Mar 14, 2015 at 9:09 PM, Philippe Verdy <verdy_p at wanadoo.fr> wrote:

> I suppose that the "short" form will differentiate from the non short
> form, only by stripping zeroes
>

That's an option to shorten these strings, but there seems to be other
requirements according to initial poster:

 On Tue, Mar 10, 2015 at 9:27 PM, Jon Zeppieri <zeppieri at gmail.com> wrote:

> The short format is intended for the shortest representation and uses
> hour fields without
> leading zero, with optional 2-digit minutes and seconds fields.


On Sat, Mar 14, 2015 at 9:09 PM, Philippe Verdy <verdy_p at wanadoo.fr> wrote:

> (the extra comment about the possibility of precision in seconds seems not
> needed for standard timezones, it is unnecessarily verbose : the normal
> form uses BOTH the hours AND minutes, preferably in fixed format with extra
> zeroes and the appropriate localized separator between hours and minutes)
>

Depends on the usage. Some might require up to seconds precision even if
verbose.

↪ Shervin

On Sat, Mar 14, 2015 at 9:09 PM, Philippe Verdy <verdy_p at wanadoo.fr> wrote:

> I suppose that the "short" form will differentiate from the non short
> form, only by stripping zeroes
>
> So "UTC+3" is the short form of "UTC+03:00", and the "short" form for
> "UTC+03:30" is ONLY "UTC+3:30".
>
> (the extra comment about the possibility of precision in seconds seems not
> needed for standard timezones, it is unnecessarily verbose : the normal
> form uses BOTH the hours AND minutes, preferably in fixed format with extra
> zeroes and the appropriate localized separator between hours and minutes)
>
>
> 2015-03-14 3:24 GMT+01:00 Shervin Afshar <shervinafshar at gmail.com>:
>
>> This is entirely up to you, but I'm personally having a hard time seeing
>>> the value of a "short" time format with just hours and no minutes.
>>
>>
>> Not to mention the confusion this would cause with time-zones with
>> fractions of an hour; e.g. Tehran UTC+3:30 != Moscow UTC+3.
>>
>> ↪ Shervin
>>
>> On Fri, Mar 13, 2015 at 7:52 AM, Doug Ewell <doug at ewellic.org> wrote:
>>
>>> Jon Zeppieri <zeppieri at gmail dot com> wrote:
>>>
>>> > More troubling, however, is that in the general case, I don't know how
>>> > to generate the short form using this data. While it's easy to strip
>>> > out the "mm" portion of this when it's not needed, I don't know, in
>>> > general, how to deal with separators or possibly literal portions of
>>> > this pattern that should be removed along with the "mm." For example,
>>> > in this particular case, I know that I'd have to remove the colon
>>> > before the minute pattern, but I imagine that a locale could use
>>> > something like: "HH 'hours', mm 'minutes'," and I would not know to
>>> > remove the entirety of ", mm 'minutes'" without treating it as a
>>> > special case.
>>>
>>> This is entirely up to you, but I'm personally having a hard time seeing
>>> the value of a "short" time format with just hours and no minutes. Many
>>> people would see that as shortened to the point of being unusable.
>>>
>>> I realize this is orthogonal to your question.
>>>
>>> --
>>> Doug Ewell | http://ewellic.org | Thornton, CO ����
>>>
>>> _______________________________________________
>>> CLDR-Users mailing list
>>> CLDR-Users at unicode.org
>>> http://unicode.org/mailman/listinfo/cldr-users
>>>
>>
>>
>> _______________________________________________
>> CLDR-Users mailing list
>> CLDR-Users at unicode.org
>> http://unicode.org/mailman/listinfo/cldr-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20150314/bd197c6b/attachment-0001.html>