On 2026-10-22 00:46, Robert Bastian wrote:
ICU 78.1 corresponds to CLDR 48.0.0, 78.2 to 48.1.0, and 78.3 to 48.2.0
(don't ask). ICU does not publish releases for CLDR patch releases (n.n.x),
so there's no ICU 78.3.1-78.3.3. CLDR only does these patch releases for
time zone data, and ICU ships time zone updates out-of-band, as explained
before (generated with the CLDR patch releases).

Thanks, I installed the attached proposed patch to TZDB's NEWS file to try to 
record this info.


With the CLDR 49 and ICU 79 releases this
week, the relevant time zone updates will roll out to ICU devices in the
coming months, which is how long I'd recommend to keep those "hacks".

Unfortunately the temporary hacks we put into TZDB to accommodate CLDR 48.x 
break tzcode 2023d through 2026a in zic's default slim mode, and the breakage 
there is more serious because it affects UT offsets, not just time zone names 
and abbreviations. So I'm inclined to remove the temporary hack pretty soon 
after November 1.

As I understand it, after November 1 users combining out-of-date CLDR with 
up-to-date TZDB will see wrong time zone names and abbreviations for 
contemporaneous and future timestamps regardless of whether TZDB's temporary 
hacks are present. So they shouldn't mind much if we remove those hacks, as 
that will merely mean their programs will use consistently wrong time zone 
names and abbreviations for some summer 2026 timestamps as well.
From 42be76f9fd1e5e48f05d9d98076b4e1d482238d3 Mon Sep 17 00:00:00 2001
From: Paul Eggert <[email protected]>
Date: Thu, 22 Oct 2026 17:24:44 -0700
Subject: [PROPOSED] More details about 2026 CLDR+ICU versions
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* NEWS: Give more details about which CLDR and ICU versions
are affected by Canadian changes so far.  Inspired by
Robert Bastian’s email in:
https://lists.iana.org/hyperkitty/list/[email protected]/message/M6EHB7PG2KUGJBBTJB5WZEKNAKYZR6J6/
---
 NEWS | 41 ++++++++++++++++++++++++++++-------------
 1 file changed, 28 insertions(+), 13 deletions(-)

diff --git a/NEWS b/NEWS
index b2d4faf1..e5097661 100644
--- a/NEWS
+++ b/NEWS
@@ -40,7 +40,10 @@ Release 2026e - 2026-09-29 17:14:38 -0700
     its traditional abbreviation EST.  Although the change to
     permanent -05 legally takes place on 2026-10-31, temporarily model
     the change to occur on 2026-11-01 at 02:00 for the same reason as
-    other recent temporary hacks.  (Caution: see “NOTE FOR 2026b
+    other recent temporary hacks.  This new temporary hack works
+    around a limitation in Unicode CLDR 48.2.2 (2026-09-21)
+    and ICU 78.3 (2026-03-17), and is planned to be removed after
+    CLDR and ICU are fixed.  (Caution: see “NOTE FOR 2026
     TEMPORARY HACK FOR CLDR AND CANADA” below.)
 
       As the change affects both America/Winnipeg and its backward
@@ -80,8 +83,11 @@ Release 2026d - 2026-09-11 15:21:07 -0700
     Model this with its traditional abbreviation CST.  Although the
     change to permanent -06 legally took place on 2026-08-21,
     temporarily model the change to occur on 2026-11-01 at 02:00
-    for the same reason as other recent temporary hacks.  (Caution:
-    see “NOTE FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA” below.)
+    for the same reason as other recent temporary hacks.
+    This new temporary hack works around a limitation in Unicode CLDR
+    48.2.1 (2026-07-08) and and ICU 78.3 (2026-03-17), and is planned
+    to be removed after CLDR and ICU are fixed.  (Caution:
+    see “NOTE FOR 2026 TEMPORARY HACK FOR CLDR AND CANADA” below.)
     This affects only America/Inuvik as the rest of the territory is
     covered by America/Edmonton, for which the equivalent change was
     released in 2026c.
@@ -163,8 +169,11 @@ Release 2026c - 2026-07-08 10:23:58 -0700
     CST.  Although the change to permanent -06 legally took place on
     2026-06-18, temporarily model the change to occur on 2026-11-01 at
     02:00 instead, for the same reason we introduced a similarly
-    temporary hack for British Columbia in 2026b.  (Caution: see
-    “NOTE FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA” below.)
+    temporary hack for British Columbia in 2026b.  This new temporary
+    hack works around a limitation in Unicode CLDR 48.1 (2026-01-08)
+    and ICU 78.2 (2025-01-30), and is planned to be removed after CLDR
+    and ICU are fixed.  (Caution: see “NOTE FOR 2026 TEMPORARY HACK
+    FOR CLDR AND CANADA” below.)
 
       As the change affects both America/Edmonton and its backward
       compatibility link, the obsolescent setting TZ="Canada/Mountain"
@@ -230,9 +239,10 @@ Release 2026b - 2026-04-22 23:06:43 -0700
     foreseeable clock change, as it moved to permanent -07 thereafter.
     (Thanks to Arthur David Olson.)  Although the change to permanent
     -07 legally took place on 2026-03-09, temporarily model the change
-    to occur on 2026-11-01 at 02:00 instead.  This works around a
-    limitation in CLDR 48.1 (2026-01-08).  This temporary hack is
-    planned to be removed after CLDR is fixed.
+    to occur on 2026-11-01 at 02:00 instead.  This temporary hack
+    works around a limitation in Unicode CLDR 48 (2025-10-29) and
+    ICU 78 (2025-10-30), and is planned to be removed after CLDR and
+    ICU are fixed.
 
       To match longstanding practice for -07 standard time in North
       America, such as for America/Dawson, America/Dawson_Creek,
@@ -245,12 +255,13 @@ Release 2026b - 2026-04-22 23:06:43 -0700
       observing -07, and may change it to "-07" if no alphabetic
       consensus emerges.
 
-  Changes to code
+    NOTE FOR 2026 TEMPORARY HACK FOR CLDR AND CANADA:
 
-    zic no longer mishandles a last transition to a new time type.
-    NOTE FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA:
-    This temporary hack works around a Canadian timekeeping bug in
-    Unicode CLDR 48 and earlier.  Unfortunately it also causes zic
+    This temporary hack works around limitations in Unicode CLDR and
+    ICU, and is planned to be removed after CLDR and ICU are fixed.
+    See <https://cldr.unicode.org/downloads/cldr-48> and
+    <https://www.unicode.org/releases/> for 2026 changes there.
+    Unfortunately the temporary hack also causes zic in tzcode
     2023d through 2026a, in the default slim mode, to generate a
     TZif file that does not conform to Internet RFC 9636 §3.3.
     The buggy file in turn causes some TZif readers, including tzcode
@@ -261,6 +272,10 @@ Release 2026b - 2026-04-22 23:06:43 -0700
     data from more-recent tz releases.  To work around this problem
     when using these older zic versions, use ‘zic -b fat’.
 
+  Changes to code
+
+    zic no longer mishandles a last transition to a new time type.
+
     zic no longer overflows a buffer when generating a TZ string like
     "PST-167:59:58PDT-167:59:59,M11.5.6/-167:59:59,M12.5.6/-167:59:59",
     which can occur with adversarial input.  (Thanks to Naveed Khan.)
-- 
2.53.0

Reply via email to