Re: Bug#877900: How to get 24-hour time on en_US.UTF-8 locale now?
Michael Stone writes:
> On Thu, Feb 07, 2019 at 09:20:07PM +0100, Ondřej Surý wrote:
>>en_DK.UTF-8 is a good default locale?
>
> I think the suggestion of just "en" made the most sense--specify the
> language and an arbitrary set of rules that aren't tied to a specific
> country.
C.UTF-8 has the default of already existing and always being available.
Other locales are not guaranteed to be around (well, except "C").
FWIW systemd will set LANG=C.UTF-8 if no other locale is specified since
systemd 240:
* When no /etc/locale.conf file exists (and hence no locale settings
are in place), systemd will now use the "C.UTF-8" locale by default,
and set LANG= to it. This locale is supported by various
distributions including Fedora, with clear indications that upstream
glibc is going to make it available too. This locale enables UTF-8
mode by default, which appears appropriate for 2018.
That seems a reasonable choice and d-i could just use that by not
specifying any locale if the user wishes so.
(There is a small problem that getty@.service unsets LANG again.)
(And you get 24-hour time, but very strange Endian in C.UTF-8:
WEEKDAY MMM DD HH:MM:SS TZ YYYY
while en_US.UTF-8 has at least DD MMM YYYY... Having
YYYY-MM-DD HH:MM:SS[+ZZZZ]
instead would be much nicer if we were to create an arbitrary set of new
rules for a new universal "en" locale ;-) )
Ansgar
Reply to: