On Mon, 19 Oct 2026 at 15:13, Brooks Harris <[email protected]> wrote:
> The short answer is that Microsoft does not use tzdb and internally > represents timezone data in the Windows registry in its own way. So this > very likely has nothing to do with how tzdb has encoded Manitoba's change > and sounds like a bug in how Microsoft have chosen to encode the change. > > > I'm not sure that's true. As I understand it they map TzDb through CLRD: > > https://raw.githubusercontent.com/unicode-org/cldr/master/common/supplemental/windowsZones.xml > I think you may have the directionality backwards on the purpose of that file. That file is maintained by CLDR and appears to be used for mapping Windows zone definitions to TZDB identifiers, not the other way around. See its edit history: https://github.com/unicode-org/cldr/commits/main/common/supplemental/windowsZones.xml As I read it, this would allow Windows applications to identify the system's selected Windows timezone and territory, map them to a corresponding TZDB identifier, and then use that identifier to pull up any of the various localization strings that CLDR defines for each TZDB identifier. Nothing about this file says anything about the underlying timezone data itself, nor that Microsoft is somehow using this file in reverse to do any data transformations. Robert Bastian (Cc'd) is involved with CLDR and the maintenance of that file and may be able to say more if I got any of that wrong. -- Tim Parenti
