On Wed, 21 Oct 2026 at 20:50, Steven Burgoyne <[email protected]> wrote:
> everyone I consulted believes the timezone is *Pacific Time*, not > Mountain Time. While I accept the reasoning of Pacific Time being > government specific and your explanation does make sense. > > You mentioned that Alberta is Mountain Time based on what CBC had > reported. What will their time zone be when they don't observe daylight > saving time? If BC will be Mountain Time, and Alberta will be an hour > ahead, that also can't be mountain time right? > I'm not sure, and absent any clear advance guidance from national organizations like CBC, all we can really do is muse on the topic. I suspect that, in the immediate-term, for things solely internal to Canada, the terms "Pacific Time", "Mountain Time", and "Central Time" will continue to be used in broadly the same places they have been, they will just take on new meanings an hour ahead of what they meant in the winter. (An exception could be Saskatchewan, which has long called their time "Central Standard" but will find it equivalent to "Mountain" year-round in such a new system as it stands.) It's possible that that can be absolutely correct usage of those terms in Canada, while being absolutely incorrect usage south of the border in the US. Both can be true at the same time. The question is what real people will do to adapt when those terms come into conflict — which depends on whether it becomes an issue for them, when it becomes an issue, and how much of an issue it becomes. As the winter goes on, we'll start to observe more about that, but consensus may be slow to emerge: Which adaptations will people maintain or forget over next year's long 8-month summer period when timekeeping alignments look more like "business as usual"? It's also entirely possible that most or all of these changes get rolled back within a year or two, before any real consensus takes hold. Part of the reason for the problem is that BC's official name for the zone, "Pacific Time", was legislated back in 2019, when it was assumed the regulation would only take effect if the western US states were to join in. In that context, it makes sense, but in the actual current context it is instead quite ambiguous. The BC government's suggestion of "PCT" is certainly a reasonable attempt to resolve that ambiguity, which does seem to be seeing some pickup. But given their explicit deference in nomenclature for traditional MST areas and absent any harmonization with Yukon, "PCT" has the same limitations as any other province-specific moniker — akin to "BCT" or "British Columbia Time" but arguably a bit worse because its name so nearly matches a nearby time observance that actually differs. We've had similar discussions about terminology in Australia over the years, where daylight saving observance/non-observance also has a significant north/south component. Different situation in North America, of course, but a similar result of: "Same zone kinda, but not *really*." It is mainly for reasons of backwards-compatibility and global clarity (not just the US) that we are sticking with MST/CST/EST for the time being instead of PDT/MDT/CDT or PCT/ABT/MBT. Again, CLDR serves a different but related purpose and so takes a different approach. > We are preparing documents to explain everything to our customers. What > you provided has actually been helpful and we are probably going to use > some of that in the post. > I'm glad it's been helpful. Both this post and my last were perhaps longer than strictly necessary to address your concerns, but as the topic keeps coming up without much clear direction yet, I wanted to gather more complete thoughts in a single place to be able to refer others here later. -- Tim Parenti
