On 2026-07-01 15:29, Robert Bastian wrote:
The hack is not needed for OpenJDK, because they updated to the latest CLDR
version before updating to 2026b. Not every system does that, especially
because this was a minor CLDR release.

Thanks for letting us know. As I understand it, this means OpenJDK 27 (currently scheduled for September 15) will have a fix for British Columbia.

But I still see issues, as Workday doesn't use OpenJDK. They use Azul Prime, and the past is any guide British Columbia fixes are not likely to hit Azul Prime until six months after OpenJDK 27 is released. This would mean British Columbia localization would be broken in Workday until around March 2027.

Workday also uses Node.js for some of user-facing components. If that is Node.js 26.4.0 (released June 24) it should be OK. But as I understand it, Workday's components are often based on older Node.js versions, and if so British Columbia is likely to see trouble there too.

Platforms other than Azul Prime and Node.js also need looking into.

If I were UBC, I would want to see the exact set of patches from Workday demonstrating how they'll fix timekeeping and localization in British Columbia, for Azul Prime, Node.js, and any other part of their software infrastructure. And if UBC is using any Workday-based middleware I'd want to see the same thing from the middleware providers. Without that, I'd expect to see glitches, almost surely in localization, and possibly even in UT offsets, for British Columbia timestamps starting in November.

Alberta is in even worse shape here. Even TZDB hasn't rolled out Alberta patches yet, though we plan to soon. And none of the other platforms I mentioned have fixes for Alberta.


>> As I understood things then, CLDR and Java's
>> localization code and data could not handle BC standard time that is
>> 7 rather than 8 hours behind UTC
>
> This is correct for CLDR 48.1 and earlier.

Thanks for mentioning that. I didn't know that the British Columbia problem was fixed in CLDR 48.2. This means some of the commentary in TZDB was incorrect, so I fixed that by installing the attached patch into the TZDB development repository.

From 01a4bd6c4e1bd606047c55c0bda55c7e6e7ea657 Mon Sep 17 00:00:00 2001
From: Paul Eggert <[email protected]>
Date: Thu, 2 Jul 2026 09:40:58 -0700
Subject: [PROPOSED] Fix CLDR version numbers in commentary

CLDR 48.2 (2026-03-17) fixed the America/Vancouver localization
anomaly, so fix comments asserting otherwise and clarify the
distinction between 48.1 and 48.2.  (Reported by Robert Bastian.)
---
 NEWS         |  2 +-
 northamerica | 12 +++++++++---
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/NEWS b/NEWS
index 0f613604..c767e7b0 100644
--- a/NEWS
+++ b/NEWS
@@ -68,7 +68,7 @@ Release 2026b - 2026-04-22 23:06:43 -0700
     (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 v48.2 (2026-03-17).  This temporary hack is
+    limitation in CLDR 48.1 (2026-01-08).  This temporary hack is
     planned to be removed after CLDR is fixed.
 
   Changes to code
diff --git a/northamerica b/northamerica
index 18112ac1..853b1172 100644
--- a/northamerica
+++ b/northamerica
@@ -1956,7 +1956,12 @@ Zone America/Swift_Current -7:11:20 -	LMT	1905 Sep
 # use that transition date for now to work around potential CLDR limitations in
 # the meantime; see British Columbia, below.
 #
-# From Paul Eggert (2026-06-19):
+# From Paul Eggert (2026-07-02):
+# The temporary hack for Alberta is needed for CLDR 48.2 (2026-03-17)
+# and earlier, not the CLDR 48.1-and-earlier which drives BC’s temporary hack.
+# Only a few platforms track minor CLDR releases, though, so the two
+# temporary hacks have roughly the same effect in practice.
+#
 # The term “Alberta Time” is legally prescribed from yesterday until
 # 2031-06-30, when the regulation in OiC 206/2026 expires to ensure that the
 # term is reviewed by then for relevancy and need.  This plan for possible
@@ -2036,13 +2041,14 @@ Zone America/Edmonton	-7:33:52 -	LMT	1906 Sep
 # I asked the BC government for advice, with no response. For now, do this:
 #   1.	As a temporary hack, pretend that the BC law takes effect
 #	not on 2026-03-09 at 00:00, but on 2026-11-01 at 02:00.
-#	This pretense works around a limitation in CLDR v48.2 (2026-03-17),
+#	This pretense works around a limitation in CLDR 48.1 (2026-01-08),
 #	which would otherwise say the interval uses “Pacific Standard Time”.
 #	(Below, this temporary hack is marked “Temporary hack; see above.”)
 #	Strictly speaking this hack is incorrect since the interval uses
 #	standard time, but it does have the right UT offset and it
 #	works around the CLDR limitation.  We should be able to remove
-#	the temporary hack after CLDR is fixed.
+#	the temporary hack by November when there would be little point
+#	to keeping it anyway.
 #   2.	After the BC law takes effect, model the time as MST sans DST.
 #	We can change this later if another conforming non-numeric abbreviation
 #	for Pacific Time becomes more popular.  Possibilities include:
-- 
2.53.0

Reply via email to