From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Jean Louis <bugs@gnu.support>
Cc: 45608@debbugs.gnu.org
Subject: bug#45608: 28.0.50; calendar-iso-date-string: "Day 6 of week 53 of 2020"
Date: Sat, 2 Jan 2021 09:17:52 -0800 (PST) [thread overview]
Message-ID: <bed88892-2b7f-4db6-bd4c-75f80a582c3e@default> (raw)
In-Reply-To: <87eej38tfl.fsf@gnus.org>
> > (calendar-iso-date-string) gives following information on this day:
> > "Day 6 of week 53 of 2020" which I consider wrong as it is 2021 and
> > the year has 52 weeks normally, the days at begin of the new year
> > should not be considered past year.
>
> https://urldefense.com/v3/__https://en.wikipedia.org/wiki/ISO_week_date__;!!G
> qivPVa7Brio!LxlLxRzS6V8fuHzPVAnAczqQvPR708E_qdx6x3He2wfh95sRUnSwi7xVfdtCWDxz$
>
> "An ISO week-numbering year (also called ISO year informally) has 52 or
> 53 full weeks. That is 364 or 371 days instead of the usual 365 or 366
> days. The extra week is sometimes referred to as a leap week, although
> ISO 8601 does not use this term. Weeks start with Monday. Each week's
> year is the Gregorian year in which the Thursday falls. The first week
> of the year, hence, always contains 4 January. ISO week year numbering
> therefore slightly deviates from the Gregorian for some days close to 1
> January."
Very cool. Interesting. Thanks for citing that, Lars.
next prev parent reply other threads:[~2021-01-02 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 11:03 bug#45608: 28.0.50; calendar-iso-date-string: "Day 6 of week 53 of 2020" Jean Louis
2021-01-02 11:32 ` Alan Third
2021-01-02 11:33 ` Lars Ingebrigtsen
2021-01-02 17:17 ` Drew Adams [this message]
2021-01-02 18:00 ` Jean Louis
2021-01-02 11:40 ` Eli Zaretskii
2021-01-02 12:42 ` Andreas Schwab
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=bed88892-2b7f-4db6-bd4c-75f80a582c3e@default \
--to=drew.adams@oracle.com \
--cc=45608@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=larsi@gnus.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).