The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steffen Nurpmeso via TUHS <tuhs@tuhs.org>
To: John Levine via TUHS <tuhs@tuhs.org>
Cc: douglas.mcilroy@dartmouth.edu
Subject: [TUHS] Re: History of cal(1)?
Date: Tue, 23 Sep 2025 03:05:34 +0200	[thread overview]
Message-ID: <20250923010534.2L17rbeZ@steffen%sdaoden.eu> (raw)
In-Reply-To: <20250923003454.03671DD56E9A@ary.qy>

John Levine via TUHS wrote in
 <20250923003454.03671DD56E9A@ary.qy>:
 |It appears that Douglas McIlroy via TUHS <douglas.mcilroy@dartmouth.edu> \
 |said:
 |>> [cal(1)] has all the logic to adjust for 16th century
 |>> calendar changes ...  (Try "cal 9 1752")
 |>> My impression is that [it is] overimplemented.
 |>
 |>The fact that a 16th century change is illustrated by an 18th century
 |>example suggests that not quite "all the logic" is there. It's good
 |>for Great Britain and its colonies, but not elsewhere. So I'd say it's
 |>underimplemented :)
 |
 |You'll be relieved to know that ncal has addressed that omission:
 |
 |$ ncal -p
 | AL Albania        1912-11-30      IS Iceland        1700-11-16
 | AT Austria        1583-10-05      IT Italy          1582-10-04
 | AU Australia      1752-09-02      JP Japan          1918-12-18
 | BE Belgium        1582-12-14      LT Lithuania      1918-02-01
 | BG Bulgaria       1916-03-31      LU Luxembourg     1582-12-14
 | CA Canada         1752-09-02      LV Latvia         1918-02-01
 | CH Switzerland    1655-02-28      NL Netherlands    1582-12-14
 | CN China          1911-12-18      NO Norway         1700-02-18
 | CZ Czech Republic 1584-01-06      PL Poland         1582-10-04
 | DE Germany        1700-02-18      PT Portugal       1582-10-04

(In an earlier thread on this topic Mr. McIlroy threw into
the discussion that for example Germany was very much more
complicated than that.  And i said iirc something like "we
tried to keep it local by then" [actually notoriously so], and
unfortunately talked about Mors Teutonicus even, as "we more
usually than not reached the Holy Land" before reaching the holy
land, which *possibly* is the only one and true way to reach the
holy land .. if you can.  (Pffffhh, what a talk.))

 | DK Denmark        1700-02-18      RO Romania        1919-03-31
 | ES Spain          1582-10-04      RU Russia         1918-01-31
 | FI Finland        1753-02-17      SI Slovenia       1919-03-04
 | FR France         1582-12-09      SE Sweden         1753-02-17
 | GB United Kingdom 1752-09-02      TR Turkey         1926-12-18
 | GR Greece         1924-03-09     *US United States  1752-09-02
 | HU Hungary        1587-10-21      YU Yugoslavia     1919-03-04
 |
 |R's,
 |John
 |
 |PS: my point was not that it's a lot of code, but that is's a distinctive \
 |hack so one might
 |look at earlier calendar programs to see whether they also did it to \
 |try and trace the
 |chain of influence.
 --End of <20250923003454.03671DD56E9A@ary.qy>

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

  reply	other threads:[~2025-09-23  1:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 18:18 [TUHS] " Douglas McIlroy via TUHS
2025-09-23  0:34 ` [TUHS] " John Levine via TUHS
2025-09-23  1:05   ` Steffen Nurpmeso via TUHS [this message]
2025-09-23  1:50     ` Rob Pike via TUHS
2025-09-23  3:57       ` Bakul Shah via TUHS
  -- strict thread matches above, loose matches on Subject: below --
2025-09-22 16:07 Noel Chiappa via TUHS
2025-09-22 16:27 ` Cameron Míċeál Tyre via TUHS
2025-09-19  3:41 Douglas McIlroy via TUHS
2025-09-19 16:03 ` Theodore Ts'o via TUHS
2025-09-19 16:20   ` Rich Salz via TUHS
2025-09-19 16:53     ` Clem Cole via TUHS
2025-09-19 18:21       ` Theodore Ts'o via TUHS
2025-09-19 22:14         ` Warner Losh via TUHS
2025-09-25  2:22           ` John Cowan via TUHS
2025-09-25 14:07             ` Ron Natalie via TUHS
2025-09-25 14:50               ` Theodore Ts'o via TUHS
2025-09-25 15:06               ` Paul Winalski via TUHS
2025-09-25 15:09                 ` Ron Natalie via TUHS
2025-09-25 17:48                   ` Clem Cole via TUHS
2025-09-25 20:36                     ` Dave Horsfall via TUHS
2025-09-25 21:05                       ` Steffen Nurpmeso via TUHS
2025-09-25 22:14                         ` Steve Nickolas via TUHS
2025-09-26  0:22                       ` jason-tuhs--- via TUHS
2025-09-26  2:08                         ` segaloco via TUHS
2025-09-26  3:17                           ` John Levine via TUHS
2025-09-26  3:18                           ` Warner Losh via TUHS
2025-09-26  3:32                             ` segaloco via TUHS
2025-09-26 14:26                               ` Dan Cross via TUHS
2025-09-26 17:23                           ` Ron Natalie via TUHS
2025-09-18 16:53 [TUHS] " Dan Cross via TUHS
2025-09-18 17:36 ` [TUHS] " Cameron Míċeál Tyre via TUHS
2025-09-18 18:31   ` Dan Cross via TUHS
2025-09-18 19:51 ` Clem Cole via TUHS
2025-09-19 19:57   ` Dan Cross via TUHS
2025-09-20 20:35 ` John Levine via TUHS
2025-09-22 14:51   ` Dan Cross via TUHS
2025-09-22 15:05     ` Jeff Johnson via TUHS

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=20250923010534.2L17rbeZ@steffen%sdaoden.eu \
    --to=tuhs@tuhs.org \
    --cc=douglas.mcilroy@dartmouth.edu \
    --cc=steffen@sdaoden.eu \
    /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 NNTP newsgroup(s).