-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLDR-17351 Updating CLDR time zone data with IANA TZDB 2024a #3498
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -537,7 +537,8 @@ For terms of use, see http://www.unicode.org/copyright.html | |
<!-- (UTC+05:00) Ashgabat, Tashkent --> | ||
<mapZone other="West Asia Standard Time" territory="001" type="Asia/Tashkent"/> | ||
<mapZone other="West Asia Standard Time" territory="AQ" type="Antarctica/Mawson"/> | ||
<mapZone other="West Asia Standard Time" territory="KZ" type="Asia/Oral Asia/Aqtau Asia/Aqtobe Asia/Atyrau"/> | ||
<!-- Microsoft may create a new zone dedicated for Almaty and Qostanay. --> | ||
<mapZone other="West Asia Standard Time" territory="KZ" type="Asia/Oral Asia/Almaty Asia/Aqtau Asia/Aqtobe Asia/Atyrau Asia/Qostanay"/> | ||
<mapZone other="West Asia Standard Time" territory="MV" type="Indian/Maldives"/> | ||
<mapZone other="West Asia Standard Time" territory="TF" type="Indian/Kerguelen"/> | ||
<mapZone other="West Asia Standard Time" territory="TJ" type="Asia/Dushanbe"/> | ||
|
@@ -569,13 +570,12 @@ For terms of use, see http://www.unicode.org/copyright.html | |
<mapZone other="Nepal Standard Time" territory="001" type="Asia/Katmandu"/> | ||
<mapZone other="Nepal Standard Time" territory="NP" type="Asia/Katmandu"/> | ||
|
||
<!-- (UTC+06:00) Astana --> | ||
<mapZone other="Central Asia Standard Time" territory="001" type="Asia/Almaty"/> | ||
<!-- (UTC+06:00) Astana --> <!-- Microsoft probably keeps Central Asia Standard Time, but change Astana to something else. --> | ||
<mapZone other="Central Asia Standard Time" territory="001" type="Asia/Bishkek"/> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Almaty will be no longer UTC+6. Microsoft uses display text I usually pick the most populous region as 001 mapping. If we use this rule, Urumqi is the one among these zones. However, official zone for Urmuqi is actually China Standard Time (UTC+8). UTC+6 is used as "defacto" offset there. For this reason, Urmuqi might not be the zone used for 001 mapping. I picked Bishkek here. This is the second populous region among these regions. |
||
<mapZone other="Central Asia Standard Time" territory="AQ" type="Antarctica/Vostok"/> | ||
<mapZone other="Central Asia Standard Time" territory="CN" type="Asia/Urumqi"/> | ||
<mapZone other="Central Asia Standard Time" territory="IO" type="Indian/Chagos"/> | ||
<mapZone other="Central Asia Standard Time" territory="KG" type="Asia/Bishkek"/> | ||
<mapZone other="Central Asia Standard Time" territory="KZ" type="Asia/Almaty Asia/Qostanay"/> | ||
<mapZone other="Central Asia Standard Time" territory="ZZ" type="Etc/GMT-6"/> | ||
|
||
<!-- (UTC+06:00) Dhaka --> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almaty and Qostanay will use UTC+5 with no DST, same as other zones in Kazakhstan. Almaty is the most populous city in Kazakhstan, so it can be the primary zone for the region. However, I think Microsoft eventually need to create a new zone for Almaty/Qostanay to preserve historic UTC offset changes separate from this. So this is a temporary solution. This is the reason why I did not change the primary zone (Asia/Oral) in this PR. When Microsoft decide to add a new Windows zone for Almaty/Qostanay, then we will move them to the new zone.