public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "nicolas.mailhot at laposte dot net" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/4628] Provide rump locales with ISO 8601 variants for use with LC_TIME
Date: Fri, 07 Jan 2022 09:48:38 +0000	[thread overview]
Message-ID: <bug-4628-716-meffVnm43q@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-4628-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=4628

--- Comment #23 from Nicolas Mailhot <nicolas.mailhot at laposte dot net> ---
Really the whole thing has been blown out of proportion by people who did not
want to work on this, piling strawmen over strawmen.

People asked to have the choice to use a new standard way of presenting time
and dates, a way that has been normalised by ISO, IETF, W3C etc, a way that has
been available by default in other OSes for about 20 years, a way that works
better for human and for software (because it sorts properly).

In other words, exactly what happened before when people switched to 24h time,
but to read some comments implementing 24h time would have required switching
all locales to some fake C unilocale, translating hour names into “neutral”
English.

All people ask for is switching numeric representations to a common format
(yyyy-mm-dd, standard iso weeks…), keeping human day names as-is. 

The only part remotely controversial are iso weeks starting on monday but they
are mostly used by businesses and businesses are the first ones to clamour for
something that does not break when you pass a border (and besides most locales
interested in ISO 8601 dates are already using ISO weeks).

And if locale structure as it exists today is badly suited to this need maybe
locale structure needs to evolve to keep up with human needs?

Unfortunately, free software continues to be unfriendly to non-US users. I
don’t know why its the case, but it’s the sole system that still has problems
selecting A4 paper or distinguishing between input system and input language.
All things MS solved in Office and Windows circa 1995.

Makes you proud of the people that managed the switch to UTF-8 given how
controversial those changes seem to be there (they are not controversial in
other OSes).

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-01-07  9:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-4628-716@http.sourceware.org/bugzilla/>
2016-02-04 13:57 ` fweimer at redhat dot com
2016-05-20 12:44 ` fweimer at redhat dot com
2016-05-20 12:44 ` dwmw2 at infradead dot org
2016-05-20 13:20 ` nicolas.mailhot at laposte dot net
2016-05-20 13:55 ` carlos at redhat dot com
2016-05-20 13:59 ` fweimer at redhat dot com
2016-05-20 14:04 ` carlos at redhat dot com
2016-05-20 19:13 ` vapier at sourceware dot org
2016-05-20 19:13 ` carlos at redhat dot com
2016-05-20 22:36 ` gunnarhj at ubuntu dot com
2016-05-20 22:37 ` carlos at redhat dot com
2016-05-20 23:28 ` gunnarhj at ubuntu dot com
2017-08-02 13:57 ` yjf.victor at foxmail dot com
2018-06-24  0:50 ` joerg_bugzilla_sourceware at reisenweber dot net
2018-06-24  0:55 ` joerg_bugzilla_sourceware at reisenweber dot net
2021-12-21 14:18 ` dwmw2 at infradead dot org
2022-01-06 22:03 ` carlos at redhat dot com
2022-01-06 22:04 ` carlos at redhat dot com
2022-01-06 22:04 ` carlos at redhat dot com
2022-01-06 22:04 ` carlos at redhat dot com
2022-01-07  9:48 ` nicolas.mailhot at laposte dot net [this message]
2022-01-07 10:58 ` dwmw2 at infradead dot org
2022-01-07 11:29 ` nicolas.mailhot at laposte dot net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-4628-716-meffVnm43q@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).