From: Eli Zaretskii <eliz@gnu.org>
To: <david@ngdr.net>
Cc: 52934-done@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#52934: format-time-string year error
Date: Sun, 02 Jan 2022 09:32:49 +0200 [thread overview]
Message-ID: <83r19qegny.fsf@gnu.org> (raw)
In-Reply-To: <ff9f0802e47206f952aed57245637db4@127.0.0.1> (david@ngdr.net)
> Date: Sat, 01 Jan 2022 16:01:21 -0700
> From: <david@ngdr.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, <52934@debbugs.gnu.org>
>
> Now I have read about ISO 8601 in Wikipedia and, of course, your replies
> are correct; now I know that we are in week 52 of 2021.
>
> However, someone writing Emacs code to produce a timestamp for, e.g.,
> .html code, does not see the need to study an ISO specification to avoid a
> tripwire that is not even obvious - the problem only occurs, if it occurs,
> in a few days of the year. Otherwise there is no reason to suspect that
> personal code is faulty: it will perform correctly, including under test,
> for about 360 days of the year.
>
> I should like to suggest a note in the Emacs Info documentation that warns
> the reader that ISO weeks do not map nicely into the calendar that the
> reader lives by. That would be helpful. I am not suggesting that the
> Emacs documentation should describe ISO 8601, only that it warns of the
> potential problems, and, ideally, gives a reference to a description of the
> standard.
I enhanced the documentation, thanks. Pointing to the ISO standard
would not be useful, since it is not freely available, so I said
something about the rules instead.
I'm therefore closing this bug.
prev parent reply other threads:[~2022-01-02 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 20:11 bug#52934: format-time-string year error david
2022-01-01 20:16 ` bug#52934: [External] : " Drew Adams
2022-01-01 20:25 ` Eli Zaretskii
2022-01-01 22:21 ` Andreas Schwab
2022-01-01 23:01 ` david
2022-01-02 7:32 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r19qegny.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52934-done@debbugs.gnu.org \
--cc=david@ngdr.net \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).