all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Antoine Beaupré" <anarcat@debian.org>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: 53396@debbugs.gnu.org
Subject: bug#53396: 27.1; icalendar rendering should include timezone
Date: Wed, 08 Jun 2022 09:20:01 -0400	[thread overview]
Message-ID: <87wndrpa0u.fsf@curie.anarc.at> (raw)
In-Reply-To: <83fskf6fu8.fsf@gnu.org>

On 2022-06-08 05:37:03, Eli Zaretskii wrote:
>> Resent-From: Stefan Kangas <stefan@marxist.se>
>> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
>> Resent-CC: bug-gnu-emacs@gnu.org
>> Resent-Sender: help-debbugs@gnu.org
>> Cc: 53396@debbugs.gnu.org
>> From: Stefan Kangas <stefan@marxist.se>
>> Date: Tue, 7 Jun 2022 17:04:10 -0500
>> 
>> Antoine Beaupré <anarcat@debian.org> writes:
>> 
>> >  1. the default date format is American. I understand Americans first
>> >     built Emacs, but its use has largely spread outside of the United
>> >     States of America which has another, standard, time format called
>> >     ISO 8601. workaround: (setq calendar-date-style 'iso)
>> 
>> Why not change the `calendar-date-style' default to `iso'?
>> 
>> It seems overly US-centric to prefer `american' when most of the rest of
>> the world does not use that particular style.
>
> IMNSHO, 'iso' is a bad default because no one uses it.

That's a strange comment after one user telling you explicitly that they
use it.

How big is that "no one" group in your mind anyways? It's at least one,
I suspect it's more.

It's even more bizarre to state that the actual ISO 8601 standard is
used by "no one" considering it's, well, an ISO standard. According to
Wikipedia:

    On the Internet, the World Wide Web Consortium (W3C) uses the IETF
    standard based on ISO 8601 in defining a profile of the standard
    that restricts the supported date and time formats to reduce the
    chance of error and the complexity of software.

Also:

   The ISO 8601 week date, as of 2006, appeared in its basic form on
   major brand commercial packaging in the United States.

The article goes on documenting 42 different countries, including the
United States of America, which have formally adopted ISO 8601 as a
national standard (ANSI INCITS 30-1997 (R2008) and NIST FIPS PUB 4-2,
specifically, in the US).

https://en.wikipedia.org/wiki/ISO_8601#Usage

So, really, "no one uses it"? Come on.

> If we don't want to be "US-centric", we should determine the default
> from the user's locale.

I'm fine with that too, but I would point out that you already have a
lot of people in the US that are pretty tired with the ridiculous locale
en_US has adopted. But maybe that debate is better left to the locale
settings and not here.

I would also argue that switching to the user's locale is harder to do
than just change the default to something that everyone will
unambiguously understand, even, yes, US people that are hell bent on not
adopting that standard.

The point I was trying to make is the default is unreasonable, and that
ISO would be a better default. But maybe that's too tough of a pill to
swallow, still, after 30 years of ISO 8601 and even more decades of
trying to internationalise software.

a.





  reply	other threads:[~2022-06-08 13:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 19:59 bug#53396: 27.1; icalendar rendering should include timezone Antoine Beaupré
2022-01-21 10:16 ` Lars Ingebrigtsen
2022-01-21 14:33   ` Antoine Beaupré
2022-01-22 11:29     ` Lars Ingebrigtsen
2022-01-23 21:04       ` Antoine Beaupré
2022-01-24  9:41         ` Lars Ingebrigtsen
2022-06-07 22:04 ` Stefan Kangas
2022-06-08  2:37   ` Eli Zaretskii
2022-06-08 13:20     ` Antoine Beaupré [this message]
2022-06-08 14:19       ` Eli Zaretskii
2022-06-08 15:33         ` Antoine Beaupré
2022-06-13 12:11     ` Stefan Kangas
2022-06-11 17:08   ` Alexander Adolf

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=87wndrpa0u.fsf@curie.anarc.at \
    --to=anarcat@debian.org \
    --cc=53396@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefan@marxist.se \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.