Re: [PATCH] en_US: define date_fmt (bug 24046)

[Aurelien Jarno <aurelien at aurel32 dot net>]

On 2019-01-03 00:23, Rafal Luzynski wrote:
> 2.01.2019 18:41 Aurelien Jarno <aurelien@aurel32.net> wrote:
> > 
> > On 2018-12-31 19:16, Rafal Luzynski wrote:
> > > 31.12.2018 12:07 Aurelien Jarno <aurelien@aurel32.net> wrote:
> > > > 
> > [...]
> > By looking at the difference between d_t_fmt and date_fmt in the locales
> > having both, it seems to me that the later has been added to display the
> > full date and time, including the timezone.
> 
> I have the same impression looking at the C locale.
> 
> > Indeed for countries that
> > only span a single timezone, it is usually not displayed.
> 
> I didn't think about it as a matter of whether a country spans one or
> multiple time zones.  I think that if you are asking about the current
> time of your desktop computer then it is in the same time zone as you
> no matter how large is your country.  OTOH, if you are asking about the
> current time of a remote computer it is not helpful that your country
> has only one time zone because the computer may be abroad.  But my
> reasoning may be wrong, feel free to disagree.
> 

My point was that country spanning multiple time zones usually (or
should?) already have the time zone indicated in d_t_fmt, so d_t_fmt and
date_fmt should be the same. At least that was my impression looking
only at a few locales.

However after grepping the existing locales, it is not that clear
anymore. The presence of %z or %Z in d_t_fmt seems mostly random. And
often different in t_fmt...

Regards,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net