Bug#877900: How to get 24-hour time on en_US.UTF-8 locale now?
On 2019-02-07 14:55, Roman Mamedov wrote:
> So for those of us (the entire world), who have been relying on this behavior:
>
> > * en_US (.UTF-8) is used as the default English locale for all places that
> > don't have a specific variant (and often even then). Generally, technical
> > users use English as a system locale
Please note that the en_US.UTF-8 locale had the 12-hour time for more
than 20 years, for all applications but the date utility. Therefore this
locale was not a reliable way to get a 24-hour time format.
> How do we roll-back what you have done here, and still get en_US.UTF-8 while
> retaining the proper 24-hour time?
>
> dpkg-reconfigure locales does not list "C.UTF-8" in the main "locales to
> generate" list, but does offer it on the next screen as "Default locale for the
> system environment". After selecting it, we get:
>
> # locale
> LANG=C.UTF-8
> LANGUAGE=
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=en_US.UTF-8
What is the content of /etc/default/locale? it looks like you have an
additional entry than the LANG one set by dpkg-reconfigure locales.
Also note that you can edit that file and chose a different locale for
each entry, so you can have for example a POSIX way of representing the
time, using a Turkish collation and with a Chilean monetary symbol.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: