Date: Fri, 6 Mar 2026 14:11:13 -0800
From: Paul Eggert via tz <[email protected]>
Message-ID: <[email protected]>
| Unfortunately if we wait for common usage to be demonstrated for the
| Vancouver area we'll have to wait for months, and for reasons I hope are
| obvious we shouldn't do that - certainly not until November.
The reasons aren't obvious to me.
As best I can tell, using the current tzdata (the gtz version, if it matters,
which it doesn't for this):
jacaranda$ TZ=America/Vancouver date
Fri Mar 6 14:50:33 PST 2026
jacaranda$ TZ=America/Vancouver date -d '+ 4 days'
Tue Mar 10 15:50:49 PDT 2026
which as best I can tell is correct, with the possible minor exception
of "PDT" instead of "we don't know yet", and tm_isdst==1 (which I am
fairly sure the act/regulation/order/... says nothing about at all).
This looks to me not to really be a "hurry and make a change so it can
operate next week" but "hurry and make a change that will apply towards
the end of the year, but needs to be made now before our authority to do
it is removed".
That is, there is really no urgency for either the tz project, or CLDR,
to do anything at all (this month anyway, or next for that matter).
Further, your desire to follow the letter of the law is kind of quaint,
given that you changed "EST" (for Australia/Melbourne) to be AEST/AEDT
despite the law (an act of the applicable Parliament) calling the times
"Eastern Standard Time" and "Eastern Summer Time" (no mention of either
"Australia" or "Daylight" - but instead relied upon information for
foreign tourists provided on some web page).
kre
