Re: [tz] Unicode CLDR supplemental/windowsZones.xml update? -Brooks Harris
On 2024-05-26 12:44, Brooks Harris wrote:
Hi Pail, On 2024-05-26 03:37 PM, Paul Eggert wrote:
On 2024-05-26 12:30, Brooks Harris via tz wrote:
What is the best procedure to obtain the latest windowsZones.xml?
https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZon...
This file is identical to the old one I have and does not reflect the commits you referred me to.
That's not a file, it's a bunch of info about the file. The info includes the file contents and a bunch of other stuff. If you just want the file, click the Raw button.
Is there a record of earlier versions? https://github.com/unicode-org/cldr/commits/main/common/supplemental/windows...
These are reachable from the earlier URL I emailed.
Right, but no version of windowsZones.xml I can find has those commits applied.
? Those changes are visible to me via that URL. Anyway, try clicking the "Raw" button. It should give you this URL: https://raw.githubusercontent.com/unicode-org/cldr/main/common/supplemental/... and I see the changes there too.
On 2024-05-26 04:12 PM, Paul Eggert wrote:
On 2024-05-26 12:44, Brooks Harris wrote:
Hi Pail, On 2024-05-26 03:37 PM, Paul Eggert wrote:
On 2024-05-26 12:30, Brooks Harris via tz wrote:
What is the best procedure to obtain the latest windowsZones.xml?
https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZon...
This file is identical to the old one I have and does not reflect the commits you referred me to.
That's not a file, it's a bunch of info about the file. The info includes the file contents and a bunch of other stuff. If you just want the file, click the Raw button. OK, I'm feeling stupid. I hit the RAW button and I see the same 2021a file. No matter what I do, and I've tried lots of things, refresh, restart browsers, all that stuff, and I see this same file again and again.
Is there a record of earlier versions? https://github.com/unicode-org/cldr/commits/main/common/supplemental/windows...
These are reachable from the earlier URL I emailed.
Right, but no version of windowsZones.xml I can find has those commits applied.
? Those changes are visible to me via that URL.
Anyway, try clicking the "Raw" button. It should give you this URL:
https://raw.githubusercontent.com/unicode-org/cldr/main/common/supplemental/...
and I see the changes there too. I'm just not seeing those changes. I do not understand why yet.
I see the file with the line <mapTimezones otherVersion="7e11800" typeVersion="2021a"> And the same 798 lines. Has there been some sort of time anomaly where I've been frozen in 2021? Thanks for getting back. Seems to be my pilot error, I'll work on it.
Duh. Yup. I didn't look carefully enough at the file from clrd-release-45. It did confuse me because is does have the same line: <mapTimezones otherVersion="7e11800" typeVersion="2021a"> And it's the same length. But the changes are there. Seems like that line should update? Anyway, thanks. On 2024-05-26 04:34 PM, Brooks Harris via tz wrote:
On 2024-05-26 04:12 PM, Paul Eggert wrote:
On 2024-05-26 12:44, Brooks Harris wrote:
Hi Pail, On 2024-05-26 03:37 PM, Paul Eggert wrote:
On 2024-05-26 12:30, Brooks Harris via tz wrote:
What is the best procedure to obtain the latest windowsZones.xml?
https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZon...
This file is identical to the old one I have and does not reflect the commits you referred me to.
That's not a file, it's a bunch of info about the file. The info includes the file contents and a bunch of other stuff. If you just want the file, click the Raw button. OK, I'm feeling stupid. I hit the RAW button and I see the same 2021a file. No matter what I do, and I've tried lots of things, refresh, restart browsers, all that stuff, and I see this same file again and again.
Is there a record of earlier versions? https://github.com/unicode-org/cldr/commits/main/common/supplemental/windows...
These are reachable from the earlier URL I emailed.
Right, but no version of windowsZones.xml I can find has those commits applied.
? Those changes are visible to me via that URL.
Anyway, try clicking the "Raw" button. It should give you this URL:
https://raw.githubusercontent.com/unicode-org/cldr/main/common/supplemental/...
and I see the changes there too. I'm just not seeing those changes. I do not understand why yet.
I see the file with the line <mapTimezones otherVersion="7e11800" typeVersion="2021a"> And the same 798 lines.
Has there been some sort of time anomaly where I've been frozen in 2021?
Thanks for getting back. Seems to be my pilot error, I'll work on it.
On 2024-05-26 14:54, Brooks Harris via tz wrote:
Duh. Yup. I didn't look carefully enough at the file from clrd-release-45. It did confuse me because is does have the same line: <mapTimezones otherVersion="7e11800" typeVersion="2021a"> And it's the same length. But the changes are there. Seems like that line should update?
On 2024-05-26 04:34 PM, Brooks Harris via tz wrote:
On 2024-05-26 04:12 PM, Paul Eggert wrote:
On 2024-05-26 12:44, Brooks Harris wrote:
Hi Pail, On 2024-05-26 03:37 PM, Paul Eggert wrote:
On 2024-05-26 12:30, Brooks Harris via tz wrote:
What is the best procedure to obtain the latest windowsZones.xml?
https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZon...
This file is identical to the old one I have and does not reflect the commits you referred me to.
That's not a file, it's a bunch of info about the file. The info includes the file contents and a bunch of other stuff. If you just want the file, click the Raw button.
OK, I'm feeling stupid. I hit the RAW button and I see the same 2021a file. No matter what I do, and I've tried lots of things, refresh, restart browsers, all that stuff, and I see this same file again and again.
Is there a record of earlier versions? https://github.com/unicode-org/cldr/commits/main/common/supplemental/windows... These are reachable from the earlier URL I emailed. Right, but no version of windowsZones.xml I can find has those commits applied.
? Those changes are visible to me via that URL. Anyway, try clicking the "Raw" button. It should give you this URL: https://raw.githubusercontent.com/unicode-org/cldr/main/common/supplemental/... and I see the changes there too.
I'm just not seeing those changes. I do not understand why yet. I see the file with the line <mapTimezones otherVersion="7e11800" typeVersion="2021a">
Look at it as just CLDR internal documentation of the timezone mapping version they use, possibly in some other tool, as it seems to be validated but not used here: https://github.com/macchiati/cldr/blob/51bd432a2060c25061966708b553163973933...
And the same 798 lines. Has there been some sort of time anomaly where I've been frozen in 2021? Thanks for getting back. Seems to be my pilot error, I'll work on it.
-- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry
On May 26, 2024, at 1:54 PM, Brooks Harris via tz <tz@iana.org> wrote:
Duh. Yup. I didn't look carefully enough at the file from clrd-release-45.
It did confuse me because is does have the same line: <mapTimezones otherVersion="7e11800" typeVersion="2021a"> And it's the same length. But the changes are there.
Seems like that line should update?
"Should be updated", more like it; it's not clear whether there's an automated process or if it's done manually. The most likely cause is that, if that line should be updated, the author of commit 9d96f340ab145003b3e6d12d95ffb16f19a8a529: https://github.com/unicode-org/cldr/commit/9d96f340ab145003b3e6d12d95ffb16f1... failed, for some reason, to update it in that commit.
On 2024-05-26 06:13 PM, Guy Harris wrote:
On May 26, 2024, at 1:54 PM, Brooks Harris via tz <tz@iana.org> wrote:
Duh. Yup. I didn't look carefully enough at the file from clrd-release-45.
It did confuse me because is does have the same line: <mapTimezones otherVersion="7e11800" typeVersion="2021a"> And it's the same length. But the changes are there.
Seems like that line should update? "Should be updated", more like it; it's not clear whether there's an automated process or if it's done manually.
The most likely cause is that, if that line should be updated, the author of commit 9d96f340ab145003b3e6d12d95ffb16f19a8a529:
https://github.com/unicode-org/cldr/commit/9d96f340ab145003b3e6d12d95ffb16f1...
failed, for some reason, to update it in that commit. I have an old version, which I don't remember or didn't comment where it came from, where that line says:
<mapTimezones otherVersion="7e11500" typeVersion="2020a"> So I really expected the later versions to be similarly updated. Hence my stupid confusion. My code tried to match that release line to the TzDb release, and failed, causing more side effects and confusion.
I got to wondering about that version line in windowsZones.xml. It is indeed inconsistent. It appears the intention is to update the line with each TzDb release, but this hasn't happened. It also appears there is not a version for each TzDb release. The TzDb version of each commit is here: cldr/tools/cldr-code/src/main/resources/org/unicode/cldr/util/data /tzdb-version.txt Paul directed me to the history of commits: Commits https://github.com/unicode-org/cldr/commits/main/common/supplemental/windows... Browse each repo to: common/supplemental/windowsZones.xml Below is the commit date, commit comment and the <mapTimezones otherVersion... line in windowsZones.xml Commits on Feb 8, 2024 CLDR-17351 Updating CLDR time zone data with IANA TZDB 2024a <mapTimezones otherVersion="7e11800" typeVersion="2021a"> Commits on Jan 11, 2024 CLDR-17295 tz2023d updates and deprecated zone/metazone cleanup (#3442) <mapTimezones otherVersion="7e11800" typeVersion="2021a"> Commits on Feb 20, 2023 CLDR-16386 Update windowsZones.xml for 2022g Mexican time zones (#2716) <mapTimezones otherVersion="7e11800" typeVersion="2021a"> Commits on May 5, 2021 CLDR-14653 Add windows zone mapping for South Sudan (Juba) (#1193) <mapTimezones otherVersion="7e11800" typeVersion="2021a"> Commits on Mar 8, 2021 CLDR-14569 Improve Windows mappings for UTC (#1086) <mapTimezones otherVersion="7e11800" typeVersion="2021a"> Commits on Feb 12, 2021 CLDR-14435 Fix mappings for BC cities without DST (#958) <mapTimezones otherVersion="7e11800" typeVersion="2021a"> Commits on Jan 26, 2021 CLDR-14434 tzdata 2021a updates (#969) <mapTimezones otherVersion="7e11800" typeVersion="2021a"> Commits on Jan 6, 2021 CLDR-14373 Updating time zone data to 2020f (#909) <mapTimezones otherVersion="7e11800" typeVersion="2020f"> Commits on Nov 18, 2020 CLDR-14301 Add new Windows time zone for Yukon Standard Time (#842) <mapTimezones otherVersion="7e11800" typeVersion="2020d"> Commits on Oct 8, 2020 CLDR-14225 tz database 2020b updates (#768) <mapTimezones otherVersion="7e11500" typeVersion="2020a"> Commits on Aug 26, 2020 CLDR-14126 Updated tz version numbers in windowsZones.xml (#670) <mapTimezones otherVersion="7e11500" typeVersion="2020a"> Commits on Apr 25, 2020 CLDR-13739 tzdata2020a updates (#440) <mapTimezones otherVersion="7e11200" typeVersion="2019b"> Commits on Aug 29, 2019 CLDR-13029 Update windowsZones.xml to 2019b level (#139) <mapTimezones otherVersion="7e11200" typeVersion="2019b"> abridged ................... Commits on Aug 25, 2015 CLDR-8774 BRS A16 - Updated time zone data to the latest. <mapTimezones otherVersion="7df0005" typeVersion="2015f"> Commits on Aug 12, 2015 CLDR-8861 Updated metazone / windows mapping for Asia/Pyongyang, updated by tzdata2015f. <mapTimezones otherVersion="7df0004" typeVersion="2015a"> abridged ................... Commits on Feb 2, 2010 CLDR-1958 Set appropriate svn properties to metaZones.xml and windowsZones.xml. <version number="$Revision$"/> <generation date="$Date$"/> <cldrVersion version="1.8"/> Commits on Feb 1, 2010 CLDR-1958 Reorganize zone mapping data - metaZones.xml/windowsZones.xml replace previous metazoneInfo.xml/wintz.xml. Updated DTD to support slightly updated data structure in these files. Modified … <version number="$Revision: 4533 $"/> <generation date="$Date: 2010-01-18 16:55:30 -0500 (Mon, 18 Jan 2010) $"/> <cldrVersion version="1.8"/> On 2024-05-26 06:45 PM, Brooks Harris via tz wrote:
On 2024-05-26 06:13 PM, Guy Harris wrote:
On May 26, 2024, at 1:54 PM, Brooks Harris via tz <tz@iana.org> wrote:
Duh. Yup. I didn't look carefully enough at the file from clrd-release-45.
It did confuse me because is does have the same line: <mapTimezones otherVersion="7e11800" typeVersion="2021a"> And it's the same length. But the changes are there.
Seems like that line should update? "Should be updated", more like it; it's not clear whether there's an automated process or if it's done manually.
The most likely cause is that, if that line should be updated, the author of commit 9d96f340ab145003b3e6d12d95ffb16f19a8a529:
https://github.com/unicode-org/cldr/commit/9d96f340ab145003b3e6d12d95ffb16f1...
failed, for some reason, to update it in that commit. I have an old version, which I don't remember or didn't comment where it came from, where that line says:
<mapTimezones otherVersion="7e11500" typeVersion="2020a">
So I really expected the later versions to be similarly updated. Hence my stupid confusion. My code tried to match that release line to the TzDb release, and failed, causing more side effects and confusion.
On 2024-05-26 23:23, Brooks Harris via tz wrote:
It appears the intention is to update the line with each TzDb release, but this hasn't happened. It also appears there is not a version for each TzDb release.
As these are all CLDR issues downstream, you might file a bug report with them. See: https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md
participants (4)
-
Brian Inglis -
Brooks Harris -
Guy Harris -
Paul Eggert