I wrote:
> Apropos of this, I just read an uber-informative post on the tz
> mailing list:
> https://lists.iana.org/hyperkitty/list/[email protected]/message/JBMDX4TTIU4HAUSDLOKKI3JRLYJZGUEG/
> So according to this apparently-very-well-informed person, TZDB is
> what is under the hood in modern Windows releases, and what we are
> doing in findtimezone.c is trying to map from their legacy
> representation back to underlying truth.  I wonder whether what we
> should really be doing is burning that code to the ground and fetching
> data from one of their modern APIs instead.  Of course question #1 is
> whether those modern APIs exist in all Windows versions we still care
> to support.

In the light of morning, that still seems like a fine idea to pursue
long-term.  But I doubt we have time to make it happen before our
November releases, and even if we did, I'd be really hesitant to
put such a change into the very last release of v14.

So what I now propose to do is commit my 0001+0003, that is just
update findtimezone.c's data to be traceable to current CLDR.
If nothing happens on the more-ambitious idea then we can add
the script from 0002 at any later time.

                        regards, tom lane


Reply via email to