3 ms·
en-dk has ISO 8601 though you're right it uses the comma. https://github.com/lattera/glibc/blob/master/localedata/locales/en_DK https://github.com/lattera/glib
by akvadrako 6y ago
en-dk has ISO 8601 though you're right it uses the comma.
https://github.com/lattera/glibc/blob/master/localedata/locales/en_DK https://github.com/lattera/glibc/blob/master/localedata/loca...
- Symbiote 6y agoThat reflects (supposedly) the official standard, but even on government forms DD-MM-YYYY or DD.MM.YYYY is used. I have never seen the ISO format used outside computer systems, unlike in Sweden where it's commonplace. It's inconsistent with da_DK, which uses DD-MM-YYYY. But there's already the decimal separator bug (writing English? dot, writing Danish? comma). % en_DK is used outside Denmark, as some sort of generic continental % European English locale. And that's the nasty hack -- this should be defined in en_EU or similar.
- akvadrako 6y agoRight, en_DK has almost nothing to do with Denmark, instead it's basically the imaginary Saneland the top poster asked for. I agree en_EU would make more sense, maybe somebody should submit a patch to glibc and in a decade it'll be safe to switch.
- SAI_Peregrinus 6y agoYou can mix and match. Unset LC_ALL, and set the following: LC_MEASUREMENT="en_DK.UTF-8" sets SI units, LC_NUMERIC="en_US.UTF-8" sets dot as decimal separator, and LC_TIME="en_CA.UTF-8" sets ISO 8601 dates and times with 24H format. But there should definitely be a saneland locale. "en_SANE.UTF-8".