On 10/21/2026 10:01 PM, Tim Parenti via tz wrote:
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.

I give BC credit for choosing an abbreviation that could easily be used outside of BC. When initially legislated in 2020 Yukon was planning on coordinating with BC (and the US state of Washington) and use the "Pacific Time" name. I have seen no attempt to call the time in Yukon "PCT". But the option to synchronize with BC is available without using "BC Time" in Yukon or "Yukon Time" in BC.

People in NWT are not in Alberta. People in Alberta are not in Saskatchewan. Both areas have chosen names that make it clear they do not want their chosen time to be known by another province's name. I expect there will be casual references to southern cities ("same time as Calgary" or "same time as Winnipeg") in conversation. I often refer to one of the four named cities (Los Angeles, Denver, Chicago or New York) when referring to time in the US ... even to locations a thousand miles away from the reference city. More people seem to know what time it is in one of those cities than in anything smaller (such as "Indianapolis"). 20 years have passed and I still meet people who think Indiana doesn't follow DST or that Indiana is 100% on Central time with no Eastern Time areas.

I support the use of the generic CST and MST in tzdata. Especially in the short term where getting the offsets right is more important.

Reply via email to