--- NEWS | 4 ++-- europe | 2 +- northamerica | 14 +++++++------- theory.html | 10 +++++----- tz-art.html | 19 +++++++------------ tz-link.html | 26 +++++++++++++------------- 6 files changed, 35 insertions(+), 40 deletions(-) diff --git a/NEWS b/NEWS index cb493fc2..36d097ee 100644 --- a/NEWS +++ b/NEWS @@ -610,7 +610,7 @@ Release 2024a - 2024-02-01 09:28:56 -0800 The leap-seconds.list file is now copied from the IERS instead of from its downstream counterpart at NIST, as the IERS version is now in the public domain too and tends to be more up-to-date. - (Thanks to Martin Burnicki for liaisoning with the IERS.) + (Thanks to Martin Burnicki for liaising with the IERS.) Changes to documentation @@ -6725,7 +6725,7 @@ few (e.g., code2012c-data2012d) have tarballs with mixed version numbers. Recent releases also come in an experimental format consisting of a single tarball tzdb-R.tar.lz with extra data. -A release's timestamp is taken from the release's commit (for newer, +A release’s timestamp is taken from the release’s commit (for newer, Git-based releases), from the newest file in the tarball (for older releases, where this info is available) or from the email announcing the release (if all else fails; these are marked with a time zone diff --git a/europe b/europe index 033b1f31..0dc31d9d 100644 --- a/europe +++ b/europe @@ -2383,7 +2383,7 @@ Zone Europe/Lisbon -0:36:45 - LMT 1884 # mainland and its adjacent islands. # # From Tim Parenti (2026-05-26): -# Observance of DST on the Azores and Madeira were explicitly covered by +# Observance of DST on the Azores and Madeira was explicitly covered by # mainland legislation in: # - Portaria 11767 of 1947-03-28 for 1947, # - Portaria 12286 of 1948-02-19 for 1948, and diff --git a/northamerica b/northamerica index 853b1172..3c53eb60 100644 --- a/northamerica +++ b/northamerica @@ -1744,17 +1744,17 @@ Zone America/Toronto -5:17:32 - LMT 1895 # From Paul Eggert (2026-05-08): # For 1916 timestamps America/Winnipeg covers only a small region. See: -# Cassidy C. Winnipeg's 100-year history with daylight time. +# Cassidy C. Winnipeg’s 110-year history with daylight time. # Winnipeg Free Press. 2026-05-06. # https://www.winnipegfreepress.com/our-communities/correspondents/2026/05/06/... -# Of the 1916 experiment, Cassidy writes: "As rural areas and nearby +# Of the 1916 experiment, Cassidy writes: “As rural areas and nearby # urban centres such as Selkirk and Brandon did not adopt DST, the -# City of Winnipeg essentially had its own time zone." Cassidy also +# City of Winnipeg essentially had its own time zone.” Cassidy also # writes that province-wide DST came into effect on 1963-05-12. # # Shanks & Pottenger write that Winnipeg did not observe DST in 1964 and 1965. -# Although dubious in the light of Cassidy's article, we lack a better source. -# Perhaps S&P's data are for the train stations, not for the city? +# Although dubious in the light of Cassidy’s article, we lack a better source. +# Perhaps S&P’s data are for the train stations, not for the city? # Also, S&P say Manitoba switched at 02:00 (not 02:00s) starting in 1966. # Since 02:00s is clearly correct for 1967 on, assume 02:00s in 1966 too. @@ -1935,7 +1935,7 @@ Zone America/Swift_Current -7:11:20 - LMT 1905 Sep # From Tim Parenti (2026-04-23): # Section 3 of Bill 31, the Red Tape Reduction Statutes Amendment Act, 2026 # https://docs.assembly.ab.ca/LADDAR_files/docs/bills/bill/legislature_31/sess... -# would repeal the Daylight Saving Time Act in the Revised Statues of Alberta +# would repeal the Daylight Saving Time Act in the Revised Statutes of Alberta # 2000 Chapter D-5: # https://kings-printer.alberta.ca/documents/Acts/D05.pdf # ...and substitutes a new chapter with language that closely parallels the @@ -2481,7 +2481,7 @@ Zone America/Inuvik 0 - -00 1953 # Inuvik founded -8:00 NT_YK P%sT 1979 Apr lastSun 2:00 -7:00 NT_YK M%sT 1980 -7:00 Canada M%sT -# Assuming Northwest Territories follow Alberta in abolishing seasonal time +# Assuming Northwest Territories follows Alberta in abolishing seasonal time # changes, replace the above line with something like: # -7:00 Canada M%sT 2026 Nov 1 2:00 # -6:00 - CST diff --git a/theory.html b/theory.html index e42c15b5..8f76aaf0 100644 --- a/theory.html +++ b/theory.html @@ -592,10 +592,10 @@ in decreasing order of importance: locations while uninhabited. The leading "<code>-</code>" is a flag that the <abbr>UT</abbr> offset is in some sense undefined; this notation is derived - from <a href="https://www.rfc-editor.org/rfc/rfc3339">Internet + from <a href="https://www.rfc-editor.org/info/rfc3339/">Internet <abbr title="Request For Comments">RFC</abbr> 3339</a>. (The abbreviation Z that - <a href="https://www.rfc-editor.org/rfc/rfc9557">Internet + <a href="https://www.rfc-editor.org/info/rfc9557/">Internet <abbr>RFC</abbr> 9557</a> uses for this concept would violate the POSIX requirement of at least three characters in an abbreviation.) @@ -657,7 +657,7 @@ Errors in the <code><abbr>tz</abbr></code> database arise from many sources: zones at all, often not even a stable landscape of mean times, prior to the middle decades of the twentieth century”. See: Timothy Shenk, <a -href="https://dissentmagazine.org/blog/booked-a-global-history-of-time-vanessa-ogle/">Booked: +href="https://dissentmagazine.org/online_articles/booked-a-global-history-of-time-vanessa-ogle/">Booked: A Global History of Time</a>. <cite>Dissent</cite> 2015-12-17. </li> <li> @@ -1128,7 +1128,7 @@ However POSIX.1-2024, like earlier POSIX editions, has some limitations: the name of a file from which time-related information is read. The file’s format is <dfn><abbr>TZif</abbr></dfn>, a timezone information format that contains binary data; see - <a href="https://www.rfc-editor.org/rfc/rfc9636">Internet + <a href="https://www.rfc-editor.org/info/rfc9636/">Internet <abbr>RFC</abbr> 9636</a>. The daylight saving time rules to be used for a particular timezone are encoded in the @@ -1558,7 +1558,7 @@ Sources for time on other planets: Michael Allison and Robert Schmunk, “<a href="https://www.giss.nasa.gov/tools/mars24/help/notes.html">Technical Notes on Mars Solar Time as Adopted by the Mars24 Sunclock</a>” - (2020-03-08). + (2023-05-15). </li> <li> Zara Mirmalek, diff --git a/tz-art.html b/tz-art.html index cbf9c587..77c7983c 100644 --- a/tz-art.html +++ b/tz-art.html @@ -207,6 +207,7 @@ episode 3, Netflix, 2020-12-26. During a New Year’s Eve journey, a software update glitch causes the Magic School Bus and its passengers to transform every time they cross time zone boundaries. The visit to the South Pole is especially tricky. +</li> </ul> <h2>Books, plays, and magazines</h2> <ul> @@ -487,20 +488,16 @@ The related book <em>What If?</em> has an entry “<a href="https://what-if.xkcd.com/26/">Leap Seconds</a>” (2012-12-31). </li> <li> -Pig kills time in <a -href="https://www.gocomics.com/pearlsbeforeswine/2016/11/06"><em>Pearls -Before Swine</em> (2016-11-06)</a>. +Pig kills time in <em>Pearls Before Swine</em> (2016-11-06). </li> <li> -Stonehenge is abandoned in <a -href="https://www.gocomics.com/nonsequitur/2017/03/12"><em>Non Sequitur</em> -(2017-03-12)</a>. +Stonehenge is abandoned in <em>Non Sequitur</em> (2017-03-12). </li> <li> Caulfield proposes changing clocks just once a year in -<a href="https://www.gocomics.com/frazz/2023/12/31"><em>Frazz</em> -(2023-12-31)</a>, while Peter and Jason go multi-lingual and -zonal in -<a href="https://www.gocomics.com/foxtrot/2023/12/31"><em>FoxTrot</em> +<em>Frazz</em> (2023-12-31), +while Peter and Jason go multi-lingual and -zonal in +<a href="https://foxtrot.com/2023/12/31/toasty/"><em>FoxTrot</em> (the same day)</a>. </li> <li> @@ -509,9 +506,7 @@ Peppermint Patty: “What if the world comes to an end tonight, Marcie?” Marcie: “I promise there’ll be a tomorrow, sir ... in fact, it’s already tomorrow in Australia!” <br> -(Charles M. Schulz, -<a href="https://www.gocomics.com/peanuts/1980/06/13"><em>Peanuts</em>, -1980-06-13</a>) +(Charles M. Schulz, <em>Peanuts</em>, 1980-06-13) </li> </ul> <h2>Jokes</h2> diff --git a/tz-link.html b/tz-link.html index d20e41d0..2a7da95e 100644 --- a/tz-link.html +++ b/tz-link.html @@ -199,7 +199,7 @@ After obtaining the code and data files, see the The code lets you compile the <code><abbr>tz</abbr></code> source files into machine-readable binary files, one for each location. The binary file format is specified by -<a href="https://www.rfc-editor.org/rfc/rfc9636">The +<a href="https://www.rfc-editor.org/info/rfc9636/">The Time Zone Information Format (<abbr>TZif</abbr>)</a> (Internet <abbr title="Request For Comments">RFC</abbr> 9636). The code also lets @@ -268,7 +268,7 @@ Studio Code</a>. </p> <p> For further information about updates, please see -<a href="https://www.rfc-editor.org/rfc/rfc6557">Procedures for +<a href="https://www.rfc-editor.org/info/rfc6557/">Procedures for Maintaining the Time Zone Database</a> (Internet <abbr>RFC</abbr> 6557). More detail can be found in <a href="theory.html">Theory and pragmatics of the @@ -385,22 +385,22 @@ calculates the current time difference between locations.</li> <section> <h2 id="protocols">Network protocols for <code><abbr>tz</abbr></code> data</h2> <ul> -<li><a href="https://www.rfc-editor.org/rfc/rfc7808">Time Zone +<li><a href="https://www.rfc-editor.org/info/rfc7808/">Time Zone Data Distribution Service</a> (Internet <abbr>RFC</abbr> 7808) is associated with -<a href="https://www.rfc-editor.org/rfc/rfc7809">CalDAV</a> +<a href="https://www.rfc-editor.org/info/rfc7809/">CalDAV</a> (Internet <abbr>RFC</abbr> 7809), a calendar access protocol for transferring time zone data by reference.</li> -<li>The <a href="https://www.rfc-editor.org/rfc/rfc5545">iCalendar format</a> -(Internet <abbr>RFC</abbr> 5445) +<li>The <a href="https://www.rfc-editor.org/info/rfc5545/">iCalendar format</a> +(Internet <abbr>RFC</abbr> 5545) covers time zone data; see its VTIMEZONE calendar component. The iCalendar format requires specialized parsers and generators; a -variant <a href="https://www.rfc-editor.org/rfc/rfc6321">xCal</a> +variant <a href="https://www.rfc-editor.org/info/rfc6321/">xCal</a> (Internet <abbr>RFC</abbr> 6321) uses <a href="https://www.w3.org/XML/"><abbr title="Extensible Markup Language">XML</abbr></a> format, and a variant -<a href="https://www.rfc-editor.org/rfc/rfc7265">jCal</a> +<a href="https://www.rfc-editor.org/info/rfc7265/">jCal</a> (Internet <abbr>RFC</abbr> 7265) uses <a href="https://www.json.org/json-en.html"><abbr title="JavaScript Object Notation">JSON</abbr></a> format.</li> @@ -1042,7 +1042,7 @@ title="Institute of Electrical and Electronics Engineers">IEEE</abbr> 1588) can achieve submicrosecond clock accuracy on a local area network with special-purpose hardware.</li> <li><a -href="https://www.rfc-editor.org/rfc/rfc4833">Timezone +href="https://www.rfc-editor.org/info/rfc4833/">Timezone Options for <abbr title="Dynamic Host Configuration Protocol">DHCP</abbr></a> (Internet <abbr>RFC</abbr> 4833) specifies a <a @@ -1125,7 +1125,7 @@ by the <abbr>NTP</abbr> implementations mentioned above, <a href="https://github.com/google/unsmear">supports</a> conversion between <abbr>UTC</abbr> and smeared <abbr>POSIX</abbr> timestamps, and is used by major cloud service providers. However, according to -<a href="https://www.rfc-editor.org/rfc/rfc8633#section-3.7.1">§3.7.1 of +<a href="https://www.rfc-editor.org/info/rfc8633#section-3.7.1">§3.7.1 of Network Time Protocol Best Current Practices</a> (Internet <abbr>RFC</abbr> 8633), leap smearing is not suitable for applications requiring accurate <abbr>UTC</abbr> or civil time, @@ -1196,16 +1196,16 @@ interchange – Part 1: Basic rules</em></a>.</li> <a href="https://www.w3.org/TR/xmlschema/#dateTime"><abbr>XML</abbr> Schema: Datatypes – dateTime</a> specifies a format inspired by <abbr>ISO</abbr> 8601 that is in common use in <abbr>XML</abbr> data.</li> -<li><a href="https://www.rfc-editor.org/rfc/rfc5322#section-3.3">§3.3 of +<li><a href="https://www.rfc-editor.org/info/rfc5322#section-3.3">§3.3 of Internet Message Format</a> (Internet <abbr>RFC</abbr> 5322) specifies the time notation used in email and <a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol"><abbr>HTTP</abbr></a> headers.</li> <li> -<a href="https://www.rfc-editor.org/rfc/rfc3339">Date and Time +<a href="https://www.rfc-editor.org/info/rfc3339/">Date and Time on the Internet: Timestamps</a> (Internet <abbr>RFC</abbr> 3339) specifies an <abbr>ISO</abbr> 8601 profile for use in new Internet protocols. -An extension, <a href="https://www.rfc-editor.org/rfc/rfc9557">Date +An extension, <a href="https://www.rfc-editor.org/info/rfc9557/">Date and Time on the Internet: Timestamps with Additional Information</a> (Internet <abbr>RFC</abbr> 9557) extends this profile to let you specify the <code><abbr>tzdb</abbr></code> timezone of a timestamp -- 2.53.0