On 2026-10-19 01:57 PM, Tim Parenti via tz wrote:
On Mon, 19 Oct 2026 at 13:46, David via tz<[email protected]> wrote:
I’m running into an issue with Microsoft Windows time zone data and hoping
you can confirm whether this stems from tzdb itself or from Microsoft’s
conversion.
Issue summary. For the end of 2027, Windows appears to calculate the DST
end date as Thursday, January 7, 2027, instead of Friday, January 1, 2027.
This one week shift affects local time conversions around New Year’s for
Manitoba Standard Time in Microsoft’s update.
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
Background: Windows 8.1 and later derive tz data from tzdb but convert it
into the Windows registry format.
As far as we are aware, this is not true. Microsoft independently
maintains its own own proprietary database for distributing time zone data
within its ecosystem.
--
Tim Parenti