Once the situation settles down in Canada we can deal with whatever conventions that they settle on for referring to their time zones (bearing in mind that the names have to be different from the US ones wherever they have different behavior — and that we have constraints on when we do a big sweep for language data.)
Cf. https://www.unicode.org/cldr/charts/49/by_type/timezones.north_america.html (Luckily we only have acronyms in languages where people would be familiar with the acronyms.) On Tue, Oct 6, 2026 at 12:19 PM Robert Bastian <[email protected]> wrote: > CLDR's goal is to represent common usage, not the letter of the law, and > we think the most common way these zones will be referred to this winter is > their current (summer) names. These are names that users are familiar with, > and it's how this whole process has been framed from the beginning: > permanent daylight time. If new names become common this winter, we will > adopt them. > > The changes linked above effectively ignore TZDB's decision to model these > changes as new standard times. stdOffset="-06" dstOffset="-05" means: if > the active offset (as returned by TZDB) is UTC-5, use the daylight name, > even if TZDB says it's standard time (tm_isdst=false). > > These changes have been released in CLDR patches, which have rolled out > alongside 2026b-e. My Android phone is already showing me PDT/MDT/CDT for > Vancouver/Edmonton/Winnipeg this winter. > > > On Tue, 6 Oct 2026 at 20:29, Paul Eggert via tz <[email protected]> wrote: > >> On 2026-10-03 14:00, Mark Davis Ⓤ via tz wrote: >> > It would be terminally confusing for speakers of >> > English, for example, to have "13 October 2026 14:30 Pacific Time" mean >> two >> > different UTC times in different countries. >> >> Agreed, and I am looking forward (if that is the right phrase...) to >> considerable confusion about naming and abbreviations next month. >> >> What are CLDR's plans for time zone names and abbreviations for >> America/Vancouver, America/Edmonton, America/Winnipeg, and >> America/Inuvik for the CLDR release planned for later this month? I >> looked for recent updates in the CLDR public repository and found only >> the following, which don't match my expectations as they seem to >> hardwire previous timekeeping practice, not the timekeeping that starts >> next month. >> >> Evidently I'm missing something. It'd be helpful to know the plans (at >> least for American English) as I imagine people will be asking on the tz >> list about this. >> >> < >> https://github.com/unicode-org/cldr/commit/016a645a70ce48e050dba145dbf8384061fb564b> >> >> (2026-09-29) changes America/Winnipeg to use stdOffset="-06" >> dstOffset="-05". >> >> < >> https://github.com/unicode-org/cldr/commit/7b1090ada749eb29d85d64bfb6c1952671d4b1f5> >> >> (2026-09-18) changes America/Inuvik to use stdOffset="-07" >> dstOffset="-06". >> >> < >> https://github.com/unicode-org/cldr/commit/d18f9652beadcec10ff40d71556e728266d0cf07> >> >> (2026-07-08) changes America/Edmonton to use stdOffset="-07" >> dstOffset="-06". >> >> < >> https://github.com/unicode-org/cldr/commit/c8babf10d858e413b977425efbff3b746bdab294> >> >> (2026-03-07) changes America/Vancouver to use stdOffset="-08" >> dstOffset="-07". >> >
