|
From: Jochen B. <Joc...@bi...> - 2024-02-05 10:44:26
|
On 05.02.24 09:55, Bo Berglund wrote: > I really wonder why it uses this terrible illogical display with the day name > first? Because the need for global, *cross-OS* standards for a timestamp format first arose with BBSes, USENET, E-Mails and the like, and the developers of those wanted to have the "Date:" headers primarily *human*-readable (as long as the human can read English): > $ date --rfc-email > Mon, 05 Feb 2024 11:23:57 +0100 > $ LANG=C date > Mon Feb 5 11:24:03 CET 2024 > $ LANG=C date +%c > Mon Feb 5 11:24:06 2024 So the human-readable variants are *older* and more widely implemented than machine-readable or purpose-optimized ones. Be grateful that the code for *logging* is unlikely to support *localization* (to one of what, 400+?, regional human conventions) ... ;-3 > $ echo $LANG > de_DE.UTF-8 > $ date > Mo 5. Feb 11:24:22 CET 2024 > $ date +%c > Mo 05 Feb 2024 11:24:25 CET > $ LANG=fr_FR.UTF-8 date > lun. 05 févr. 2024 11:24:43 CET > $ LANG=fr_FR.UTF-8 date +%c > lun. 05 févr. 2024 11:24:50 > $ LANG=en_US.UTF-8 date +%c --date="4 hours" > Mon 05 Feb 2024 03:41:11 PM CET > $ LANG=en_GB.UTF-8 date +%c --date="4 hours" > Mon 05 Feb 2024 15:41:16 CET > $ locale -a | wc -l > 873 Kind regards, -- Jochen Bern Systemingenieur Binect GmbH |