On Wed, 21 Oct 2026 at 14:13, Steven Burgoyne via tz <[email protected]> wrote:
> On September 17, 2026 the government of BC adopted PCT instead: > https://www2.gov.bc.ca/gov/content/governments/celebrating-british-columbia/daylight-saving-time. > Can this be updated? > > People are confused seeing MST instead of PCT for future dates. > The discussion on province-specific abbreviation neologisms has been had several times over now, see: https://lists.iana.org/hyperkitty/list/[email protected]/message/YUJ6ZLVLY6TECPX7ZPXO2R64S2IVG3UD/ In short, for broader technical compatibility we prefer existing abbreviations with stable meanings unless/until something else demonstrates widespread and persistent adoption by average people coordinating events, both from inside and outside the region — not just internal government use or use by a few prominent news outlets. National and international organizations are not likely to widely adopt individualized nomenclature for each province and territory. Although we have now seen some cases of outside adoption of "PCT" in the wild, it's far too early to assert that it will (or won't!) necessarily catch on more widely. Even if its widespread adoption were already clear, it leaves open the question of whether "PCT" should also be applied to areas like Creston that have traditionally used "MST" or to Yukon which also observes equivalent time. (A similar argument can be made against blindly applying "ABT" to Saskatchewan or Northwest Territories, for that matter.) This is by no means a new problem: MST being equivalent to the US west coast for much of the year including the summer, but being an hour ahead of it in the winter, is a confusion that Arizona has successfully handled for many years now. But not without frustration and confusion both inside and outside of the state. Some amount of confusion is unavoidable, and what might be clearer to one is more confusing to another. On Wed, 21 Oct 2026 at 16:35, Brian Inglis via tz <[email protected]> wrote: > Here in Alberta, we know that SK has always used CST, so it is unlikely > anyone > will know or care what the government specified, and mentions of BC, AB, > MB time > will probably be common until next year, possibly longer. > One data point: During CBC's coverage of the Alberta referendum results on Monday, presenters referred consistently to "Mountain Time" even though the Alberta government has officially called it "Alberta Time" since 18 June. https://www.youtube.com/watch?v=p5naFQB4P9g While this is merely an observation related to timekeeping nomenclature and not intended as a political statement one way or the other, a national broadcaster choosing how best to communicate time to a national audience is nonetheless a useful data point. I don't imagine that sort of cross-provincial colloquial usage will change much soon, and this is undoubtedly a big part of why CLDR has chosen strings like "Pacific Daylight Time". To be clear, we recommend using these sorts of libraries in applications where localization is necessary. Our abbreviations mostly exist for POSIX-compliance purposes and, as structured, we can't serve different abbreviations to different people. If application developers find that these abbreviations are causing issues for their typical users, I'd suggest that they should consider making use of CLDR for true localization. If we set aside Nunavut's misalignment for the time being and assume they will eventually adjust, the new colloquial understanding could actually be quite simple. For example, the time scroller on CBCNN loops through the following times at the start of a show: 12:30 p.m. NT / 12:00 p.m. AT / 11:00 a.m. ET / 10:00 a.m. CT / 9:00 a.m. MT / 8:00 a.m. PT Starting 1 November, it's entirely plausible that it just says: 12:30 p.m. NT / 12:00 p.m. AT / 11:00 a.m. ET / 11:00 a.m. CT / 10:00 a.m. MT / 9:00 a.m. PT …with the notion that, at least for this winter, ET = CT in Canada. Simple enough, and those abbreviations may well be good enough, internal to Canada. But that is, of course, all based on one data point from one broadcaster. It's if and when that colloquial/casual usage starts to cause cross-border confusion that we'll most likely be looking at how that usage changes and what conventions may organically arise to mitigate that confusion. On some level, what that will look like is just not knowable until it happens, and until then, using established abbreviations that carry established meaning remains important. If they're exposed to end-users which causes them to pause a bit and consider more carefully how the new time zones interact without just relying on habit, that's not in and of itself a bad thing. -- Tim Parenti
