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 <[email protected]> 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, 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 2027 rule applies. There is no
> overlap between the first day of 2027 and the first Thursday of 2027. The
> 2026 rule ceases to apply on January 1st, 2027. Ignore 2026 rules in 2027.
> On 10/20/2026 12:38 AM, Matt Johnson-Pint via tz wrote:
>
> Manitoba in particular is modeled as:
>
> 2025: UTC-6 base offset, DST is +1 hour (ie., UTC-5). Start DST on 2nd
> Sunday of March at 02:00. End DST on 1st Sunday of November at 02:00
> 2026: UTC-6 base offset, DST is +1 hour (ie., UTC-5). Start DST on 2nd
> Sunday of March at 02:00. End DST on 1st Thursday of January at 00:00
> 2027: UTC-5 base offset, DST does not apply
>
> So when you read the DST end date for 2026 as being the 1st Thursday in
> January,* it doesn't mean it floats into January of 2027* - it means that
> DST ended already in January 2026. Since it was already not in effect, that
> actual date would be a no-op.  In other words, the DST delta was already 0,
> so ending it keeps it at 0.  This is a hack because of the nature of this
> data structure - but it's an effective hack.
>
> 2027 has no DST at all, it's just UTC-5 the whole year.
>
> This trick has been used in the past without issue. A good example is
> Yukon in 2020.
>
> Again - this is about the Windows registry legacy data.  It has nothing to
> do with how TZDB has modeled America/Winnipeg.  That scheme is much more
> dynamic and much more close to reality.  Just look up America/Winnipeg in
> the source data, and you'll see how it's done.
>
> Cheers,
> Matt
>
>
>

Reply via email to