I have attached a technical analysis of the Windows Architecture as it relates to the Manitoba Standard Time TZ update and a enterprise readiness guide I put together, incorporating this discussion. Any feedback is appreciated. This is for internal use only. Thanks all for your help; it's greatly appreciated! David On Thu, Oct 22, 2026 at 10:19 PM Brooks Harris wrote: > On 2026-10-22 10:58 PM, James Bellaire wrote: > > On 10/22/2026 9:45 PM, Brooks Harris via tz wrote: > > On my Windows11 Pro…
Hi folks, [All I could see in Matt's previous post was a large black rectangle! I could not see any text content until replying here.] I downloaded CLDR 49 common including Supplemental windowsZones.xml, and checked the CLDR issues log, which shows not yet applied changes, with 11 zones having different names, and 7 with different UTC offsets: https://unicode-org.atlassian.net/browse/CLDR-19872 also referring to a script PostgreSQL src/tools/win32tzlist.pl and linked output…
On 2026-10-22 10:58 PM, James Bellaire wrote: > On 10/22/2026 9:45 PM, Brooks Harris via tz wrote: >> On my Windows11 Pro 23H2 laptop I see no evidence of (UTC-07:00) >> British Columbia or (UTC-05:00) Manitoba in ether the time zone >> change pull-down or in the Registry. So, whatever time zone updates I >> might have received have not updated those parameters.  I'll watch it >> and see if and when it updates. Sure, I can run a full update, but >> I'm curious to see what other users might…
On 10/22/2026 9:45 PM, Brooks Harris via tz wrote: > On my Windows11 Pro 23H2 laptop I see no evidence of (UTC-07:00) > British Columbia or (UTC-05:00) Manitoba in ether the time zone change > pull-down or in the Registry. So, whatever time zone updates I might > have received have not updated those parameters.  I'll watch it and > see if and when it updates. Sure, I can run a full update, but I'm > curious to see what other users might be experiencing. > -Brooks Windows11 Pro 26H2…
On my Windows11 Pro 23H2 laptop I see no evidence of (UTC-07:00) British Columbia or (UTC-05:00) Manitoba in ether the time zone change pull-down or in the Registry. So, whatever time zone updates I might have received have not updated those parameters. I'll watch it and see if and when it updates. Sure, I can run a full update, but I'm curious to see what other users might be experiencing. -Brooks On 2026-10-21 11:25 PM, Matt Johnson-Pint wrote: > I really can't answer any questions about how…
Nunatsiaq News published an article today based on last week's Makivvik press release. https://nunatsiaq.com/stories/article/makivvik-wants-to-end-time-changes-in-nunavik-but-eyes-next-year-for-it/ Google search has indexed the article and now gives the correct answer (clocks falling back this November) when asked about the time change issue in Nunavik. (May all search engines give correct responses!) On 10/19/2026 7:08 PM, James Bellaire via tz wrote: > On 10/19/2026 5:29 PM, Brian Inglis via…
On 2026-10-22 00:46, Robert Bastian wrote: > ICU 78.1 corresponds to CLDR 48.0.0, 78.2 to 48.1.0, and 78.3 to 48.2.0 > (don't ask). ICU does not publish releases for CLDR patch releases (n.n.x), > so there's no ICU 78.3.1-78.3.3. CLDR only does these patch releases for > time zone data, and ICU ships time zone updates out-of-band, as explained > before (generated with the CLDR patch releases). Thanks, I installed the attached proposed patch to TZDB's NEWS file to try to record this info. > With…
On Thu, 22 Oct 2026 at 15:03, Heitor David Pinto via tz wrote: > The government of Ontario issued the regulation setting the time in the > part of the province west of 90°W as UTC-5 all year. It comes into force on > 1 November 2026. > https://www.ontario.ca/laws/regulation/r26333 Thanks; patch to commentary attached. No new zone or release needed, as 2026e already assumed this was likely. -- Tim Parenti
Hi Tim, Brooks, James, Robert, and Paul, I appreciate everyone's thorough follow-up. This discussion was extremely helpful in framing the issue correctly. My take-away is that the "First Thursday" behavior in the Windows registry is an expected, if legacy, implementation detail—effectively a placeholder to bridge the data structure requirements rather than an error in the underlying tzdb. Since 2027 is modeled as a clean transition to permanent UTC-5, there is no risk of the 2026 DST rules…
On Thu, 22 Oct 2026 at 00:36, Paul Eggert wrote: > On 2026-10-21 13:46, Robert Bastian via tz wrote: > > 78.3 is the latest ICU release (79 releases on Thursday), but ICU > provides > > data packages for TZ data that are backwards compatible back to ICU 44: > > https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew. This > way > > even old systems that cannot update ICU can receive updated time zone > data. > Things should start getting more fun after Thursday, I suppose. (Hey, >…
I really can't answer any questions about how the servicing works presently. I just checked my fully updated Windows 11, 25H2, 26200.9711 machine (I haven't updated to 26H2 yet though) - and even though I have the new registry entries, and C:\Windows\Globalization\Time Zone\timezoneMapping.xml has them too, it has an outdated ICU 72.1 and an ICU zoneinfo64.res file corresponding to 2022g. I also tested with both UWP/WinRT and .NET APIs (at least the ones that use IANA time zones), and…
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…
> On 22 Oct 2026, at 12:17, Tim Parenti via tz wrote: > > I will add that, if there is any useful semi-recurring task here that one could automate, it would be quite a light one and not really part of this project, though supportive: Whenever there is a new tz release, it would be nice to ensure that the handful of new links throughout end up being submitted to Wayback for archival if they haven't been already. This would help those future researchers when they do inevitably come across a dead…
The government of Ontario issued the regulation setting the time in the part of the province west of 90°W as UTC-5 all year. It comes into force on 1 November 2026. https://www.ontario.ca/laws/regulation/r26333
On Wed, 21 Oct 2026 at 20:50, Steven Burgoyne 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…
On Wed, 21 Oct 2026 at 18:44, Paul Eggert via tz wrote: > I'm mostly worried about dead links in our .html files. > Correct. The .html files are more "live documentation" about how the database is structured, similar or related projects, etc. so they tend to be seen by more people with passing interest in the database than serious researchers who have other tools at their disposal like the Wayback Machine. > If the target page isn't archived we > should leave the dead link alone; and arguably…
Hi Tim, Thanks for the detailed explanation and for taking the time to explain your reasoning. However, after speaking with many people, 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…
On 2026-10-20 22:49, gary-14--- via tz wrote: > I am not asking anyone to rewrite the comments. If a link check is useful, I can run it on a schedule and post only the newly dead ones. Otherwise, treat this as a note that the citations are decaying faster than the rules they document. I'm mostly worried about dead links in our .html files. For comments in other files, in a few cases I have replaced dead links with links to web.archive.org. Doing that properly requires knowing which archive.org…
On 2026-10-21 13:46, Robert Bastian via tz wrote: > 78.3 is the latest ICU release (79 releases on Thursday), but ICU provides > data packages for TZ data that are backwards compatible back to ICU 44: > https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew. This way > even old systems that cannot update ICU can receive updated time zone data. Things should start getting more fun after Thursday, I suppose. (Hey, that's tomorrow!) I'm a bit fuzzy about the relationship between CLDR…
On Wed, 21 Oct 2026 at 14:13, Steven Burgoyne via tz 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/…
> I see ICU releases through 78.3 which only goes up to tz 2026a. More recent patch releases of CLDR have followed closely behind our more recent tz releases — generally within hours and only updating tzdata — and the latest CLDR 48.2.3 has the latest tzdata 2026e. So when you say Windows/Microsoft are using tz data from ICU, does this include these other CLDR releases? 78.3 is the latest ICU release (79 releases on Thursday), but ICU provides data packages for TZ data that are backwards…
On 2026-10-20 17:44, Steven Burgoyne via tz wrote: > Our company has adopted the updated IANA standard for timezones. However, we > have run into some issues. People are getting very confused seeing MST because > of this: > > To match longstanding practice for -07 standard time in North > America, such as for America/Dawson, America/Dawson_Creek, > America/Fort_Nelson and America/Whitehorse, affected BC > timestamps use the abbreviation MST. As the change affects both > America/Vancouver and…
On Mon, 19 Oct 2026 at 23:53, Matt Johnson-Pint wrote: > Note that these posts describe Windows time zones in terms of their > "legacy" or "registry" time zone identifiers > Thanks for the detailed explanation, Matt, and for helping us speak more clearly on this and where it fits into the overall ecosystem. And thank you also for your years of service in those efforts! > TLDR: Yes, Windows uses IANA TZ data (via ICU), and it ALSO maintains its > legacy registry format because older APIs require…
Hello tz, I audited every URL cited in the comments of the tz source files (africa, antarctica, asia, australasia, backward, backzone, etcetera, europe, northamerica, southamerica, factory, leapseconds). 1,402 unique URLs. Method: one HEAD request per URL, then a GET for anything not 2xx (many hosts reject HEAD). A 2xx on either pass counts as live. For every confirmed dead link I then asked the Wayback Machine availability API whether it has a capture. Results: 776 live 200 dead…
Hello, I'm working on Brazilian historical timekeeping for an astrology program and compared the tzdb Brazil data (2026e) with the original decree texts (scans published by the Observatorio Nacional and texts from the Camara dos Deputados). I found three points. *1. End of DST on 1966-03-01 (proposed data change)* Decree 57,843 (1966-02-18, published in the DOU of 1966-02-25, p. 2117), art. 2: "O término da 'hora de verão', fixado no Decreto nº 57.303, de 22 de novembro de 1965, fica antecipado…
Our company has adopted the updated IANA standard for timezones. However, we have run into some issues. People are getting very confused seeing MST because of this: To match longstanding practice for -07 standard time in North America, such as for America/Dawson, America/Dawson_Creek, America/Fort_Nelson and America/Whitehorse, affected BC timestamps use the abbreviation MST. As the change affects both America/Vancouver and its backward compatibility link, the obsolescent setting…
Correct. The 2026 rule "First Thursday in January" only applies to 2026. It does not apply in 2027. The Windows APIs that use this data should all already be handling this correctly. If not, that's a case for Microsoft Support. Either way, it's not an issue for this mailing list to resolve. -Matt On Tue, Oct 20, 2026 at 1:22 PM James Bellaire wrote: > On 10/20/2026 12:33 AM, David via tz wrote: > > > 1. > > *The First Thursday (Jan 7) vs. First Friday (Jan 1) Boundary:* > > Because January 1,…
On 10/20/2026 12:33 AM, David via tz wrote: > > 1. > > *The First Thursday (Jan 7) vs. First Friday (Jan 1) Boundary:* > > Because January 1, 2027 is a Friday, encoding transitions using > day-of-week occurrence rules (such as the first Thursday of the > month) pushes the boundary to Thursday, January 7, 2027, leaving > the 2026 DST rule open into the first week of the new year. > If I understood the explanation correctly, the 2026 rule only applies to 2026 dates. Once a 2027 date is seen the…
On Tue, 20 Oct 2026 at 03:56, James Bellaire wrote: > Since Nunavik's announcement was only made last week and I just noticed it > within the last 24 hours, it's understandable that CBC doesn't seem to have > noticed it yet either. I'll reach out privately to a broader set of > potential CBC contacts to see if we are able to get this correction/update > on their radar. > > The most recent CBC article ( > https://www.cbc.ca/news/canada/british-columbia/what…