They could do this. But Saskatchewan observes Central Standard Time (CST) by statute. It's in The Time Act (2026) and it was also in The Time Act (1966), the prior legislation that the new act replaced. People in Saskatchewan are used to calling it CST. They won't think of us being in Midwest Canada time. Also, that risks conflating "midwest Canada" with the "Midwest" (which Americans will always think of as the US Midwest). I say we stick with the tried and true time zone labels for North…
> CLDR has bypassed the issue by using "PDT", "MDT" and "CDT" year round. Even though it is odd to have a xDT without an xST. That is just a short-term fix for CLDR. Governments really should give a much longer lead time for timezone changes, especially when it involves the creation of new timezones. My personal opinion (not speaking for the Unicode Consortium) is that the best naming convention for the new no-daylight zones that would maintain continuity with previous names as much as possible…
Numeric time seems best until Canada gets their stuff straight (or the U.S. abolishes clock switching too). I don't see an issue with Canada creating new timezone names to avoid confusion with Standard/Daylight timezones (which imply daylight savings switching). The problem is the way they've done it, with giving each province its own timezone name. And it really doesn't help that British Columbia decided to use the word 'Pacific' in their new timezone. That just confuses it with the existing…
On Thu, 12 Nov 2026 at 23:46, Brian Inglis via tz wrote: > In zonenow.tab (current time correct only going forward) on 2026-11-01 > > America/Vancouver was merged into America/Phoenix > America/Edmonton was merged into America/Mexico_City > America/Winnipeg was merged into America/Jamaica > > as those other zones have had those offsets for longest, and/or have larger > populations than the legacy Canadian zones Stepping in quickly to correct a potential misapprehension here— these changes to…
On 2026-11-12 20:19, James Bellaire via tz wrote: > On 11/12/2026 8:24 PM, Aoun Khan via tz wrote: >> I think you're ignoring the main point here: BC's new Pacific Time is just a >> name. MST is the same exact time zone, it's just a more universal name that is >> used beyond British Columbia. BC already has a TZ name (i.e. America/Vancouver). >> >> Yukon doesn't go by PCT for example. Provinces and territories are >> artificially creating different provinces (ABT vs. NWT Time). > > Paul has…
On 11/12/2026 8:24 PM, Aoun Khan via tz wrote: > I think you're ignoring the main point here: BC's new Pacific Time is just a name. MST is the same exact time zone, it's just a more universal name that is used beyond British Columbia. BC already has a TZ name (i.e. America/Vancouver). > > Yukon doesn't go by PCT for example. Provinces and territories are artificially creating different provinces (ABT vs. NWT Time). Paul has suggested an option that would remove "MST" from BC, "CST" from…
I think you're ignoring the main point here: BC's new Pacific Time is just a name. MST is the same exact time zone, it's just a more universal name that is used beyond British Columbia. BC already has a TZ name (i.e. America/Vancouver). Yukon doesn't go by PCT for example. Provinces and territories are artificially creating different provinces (ABT vs. NWT Time).
Changes to DST has been put on pause for now. Instead it looks like we're going back to the old timezone. I don't believe the details have been finalized, but this is what was approved in the parliment earlier today: On November 12, 2026, Inatsisartut (Greenland's parliament) adopted an amendment to the country's timezone legislation (EM2026/104), effectively reversing the timezone change introduced in March 2023. Under the adopted amendment, Greenland will return to its former standard…
Hello all, I apologize, to bring it back to a discussion on the merits of the change. I believe a new TZ name should be created with an update to the database because the situation in B.C. specifically (as opposed to areas to the east) satisfies all three criteria in RFC6557. According to the "Best Current Practices”: 1: "New TZ names (e.g., locations) are only to be created when the scope of the region a name was envisioned to cover is no longer accurate." — America/Vancouver and, for example,…
https://www.arctictoday.com/greenland-shifts-its-clocks-closer-to-north-america-and-further-from-denmark/ "Greenland’s parliament voted Thursday to return most of the country to the UTC-3 time zone, reversing a 2022 decision that moved Nuuk an hour closer to Europe. The bill, put forward by Siumut, passed Inatsisartut with 16 votes in favor and seven abstentions, Sermitsiaq reported. Clocks will go back two hours on October 31, 2027, when daylight saving time ends."…
I do not get to choose which laws I follow. Please follow the law and implement Pacific Time as PCT (America/Vancouver) Cheers Chris > On Nov 12, 2026, at 10:30, James Bellaire wrote: > > Take a look at Europe/Berlin. Multiple countries sharing a single zone since they all have a shared time since 1970. > > The standard for an area getting a different Zone entry is a difference in the clock on the wall time since 1970. Not local preferences or political issues. > > If MST is offensive then Paul…
Take a look at Europe/Berlin. Multiple countries sharing a single zone since they all have a shared time since 1970. The standard for an area getting a different Zone entry is a difference in the clock on the wall time since 1970. Not local preferences or political issues. If MST is offensive then Paul has offered the option of -07 for America/Vancouver and -06 for America/Edmonton. CLDR has gone with PDT and MDT. Hi James, I am sorry but I do not understand the logic here: "The ask for each…
Hi James, I am sorry but I do not understand the logic here: "The ask for each province and territory in Canada to get a unique zone for the purpose of providing a unique name is out of scope for the tzdata project.” The provinces and territories are larger than most countries and many cover more than one time zone in north america. These are the jurisdictions that control time zones in Canada and have done since WWI. The timezones have not changed in 100 years, since the advent of computers.…
Aoun Khan wrote: > If Alberta had come out and simply said "we're switching to CST from this winter" then most of this confusion wouldn't exist. It could still introduce ambiguity: is that "CST" to be interpreted as a "CST/CDT" zone, or year-round "-06". You'd need the zone name e.g. "America/Edmonton" to translate properly. > Numerical offsets are probably the least ambiguous. People will have to get used to it over time. Static=numeric makes the most sense to me, too. No need for translation…
On 11/11/2026 1:31 AM, Brian Inglis via tz wrote: > The lack of effort by application vendors, and input from > international contributors, are influencing the couple of volunteer > maintainers to switch to just straight numeric UTC offsets (format %Z > -> %z), in the hopes that applications will do their jobs better. I did a quick count and there are approximately 439 "Zone" entries in tzdata, including all regions and the back zones that exist for users/applications who want historical time…
On 2026-11-09 14:01, Payette, Graham [ISLH] via tz wrote: > Hi. Hoping to understand within which release the current “MST” workaround for > the permanent move to daylight savings time for the province of British Columbia > will move to utilizing the approved “PCT” acronym rather than “MST”. (no change > from UTC-7 but the change in acronym/identifier will help as there are now many > jurisdictions utilizing MST). > > This change was announced provincially on September 17^th > >…
Le 2026-11-09 23:52, Brian Inglis via tz a écrit : > In fact, you would probably raise fewer issues, at least from outside those provinces, if you changed those zone abbreviations to EST/-1/-2, > as at least everyone across North America would know what was meant. Most people there would probably know what was meant ... for a short time, until permanent DST comes into effect in eastern north America, as seems likely (Sunshine Protection Act, proposed Quebec changes, etc.), at which point…
The big issue is that while 100% of people would understand "Alberta Time" to mean local time in Alberta, even if they're not familiar with the new time zone name, the majority of the population has not understood that the new time zone is effectively Central Standard Time. Hence, the confusion and the flurry of complaints coming in. Part of it is that none of the provinces acknowledged the standard time zones when communicating this info to the public. Most people have to be explicitly told in…
Hello, I maintain a small astrological chart calculator that converts birth dates and times to UTC, so historical offsets for Argentina matter to us in one-minute increments. While checking our results against the ACS Atlas (through Solar Fire), we found a case where tzdata and that atlas disagree, and where tzdata's own comments suggest the data may need a second look. I am not asking for a specific change -- just flagging what we found, with sources. 1. The 1991 -04 period in…
On 2026-11-09 14:52, Brian Inglis via tz wrote: > If you do plan to change those outputs again, at least please again > coordinate timing with CLDR for major apps L14n As I understand it, CLDR does not care what abbreviations TZDB uses. That is (using TZDB terminology), CLDR cares about the UT timestamp, about the Zone name, about tm_gmtoff, and about tm_isdst, but it does not care about tm_zone. So there is no need to coordinate with CLDR about TZDB's time zone abbreviations. > I feel that…
On 2026-11-08 17:44, Paul Eggert via tz wrote: > On 2026-09-01 00:39, Paul Eggert wrote: >> This topic has come up on the tz mailing list. > To better document this topic how TZDB addresses the issue of which time zone > abbreviations to use in Alberta, BC, Manitoba, etc., I installed the attached > proposed patch to the TZDB documentation. It briefly paraphrases the email I > sent in September. > > I'm also thinking of changing the abbreviations in affected TZDB zones to be > numeric (e.g.,…
Hi. Hoping to understand within which release the current "MST" workaround for the permanent move to daylight savings time for the province of British Columbia will move to utilizing the approved "PCT" acronym rather than "MST". (no change from UTC-7 but the change in acronym/identifier will help as there are now many jurisdictions utilizing MST). This change was announced provincially on September 17th https://www2.gov.bc.ca/gov/content/governments/celebr…
No, the abbreviations have never been mentioned in law that I know of, only the name “Pacific”. Here is the March 2, 2026 order in council that actually brought the laws into force on March 6. It simply names the Interpretation Act Amendment and repeals the Daylight Savings Time regulation which had come in when the fall back/spring forward dates were moved to November and March in 2006. While the abbreviation is not mentioned in the law, it is clear from the Government’s general usage that…
On 11/9/2026 12:56 AM, Christopher Joseph Alemany wrote: > Especially given the strong wording of part (2) compared to the > original below, time in B.C. is “Pacific Time”, and according to > subsequent guidance last month from government > , > the expected abbreviation is PCT. Although I do have to laugh at the > second sentence… not so smooth. 😂 > > “Regulation brought the amendments into effect on March 8, 2026. > > Government will work closely with organizations, small businesses, and >…
I agree completely. There are not enough *ST and *DT combinations to go around. Let the people downstream come up with their own abbreviations. On 11/8/2026 7:22 PM, Doug Ewell via tz wrote: > Paul Eggert wrote: > >> I'm also thinking of changing the abbreviations in affected TZDB >> zones to be numeric (e.g., "-06" instead of "CST"/"MDT"/"ABT"/"SKT"), >> at least until things settle down (which could take quite some time). >> Numeric abbreviations are widely used, unambiguous, and would mean…
Paul Eggert wrote: > I'm also thinking of changing the abbreviations in affected TZDB > zones to be numeric (e.g., "-06" instead of "CST"/"MDT"/"ABT"/"SKT"), > at least until things settle down (which could take quite some time). > Numeric abbreviations are widely used, unambiguous, and would mean > less need to worry about this sort of thing. I would support this. I had no idea so many people apparently relied on tzdb for these values. -- Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org
On 11/8/2026 6:44 PM, Paul Eggert via tz wrote: > I'm also thinking of changing the abbreviations in affected TZDB zones > to be numeric (e.g., "-06" instead of "CST"/"MDT"/"ABT"/"SKT"), at > least until things settle down (which could take quite some time). > Numeric abbreviations are widely used, unambiguous, and would mean > less need to worry about this sort of thing. Due to the ambiguity of the zones (no consistent nationwide name) numeric abbreviations in Canada seem to be the best…
On 2026-09-01 00:39, Paul Eggert wrote: > This topic has come up on the tz mailing list. To better document this topic how TZDB addresses the issue of which time zone abbreviations to use in Alberta, BC, Manitoba, etc., I installed the attached proposed patch to the TZDB documentation. It briefly paraphrases the email I sent in September. I'm also thinking of changing the abbreviations in affected TZDB zones to be numeric (e.g., "-06" instead of "CST"/"MDT"/"ABT"/"SKT"), at least until things…
Hello, I help maintain timeandcalendars.com, a free time-zone converter, world clock, and calendar-tools site. I noticed the tz-link.html resources page lists several comparable converters (TimeZoneConverter.com, 24TimeZones, Time.is) and wanted to suggest timeandcalendars.com as an addition under the converters section, if it's a good fit. Happy to provide any more detail needed. Thanks for maintaining such a valuable resource for the developer community. Regards, Jose timeandcalendars.com