[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #10117(new unknown)

Opened 3 weeks ago

Last modified 9 days ago

Missing Mapping in "windowsZones.xml"

Reported by: robert.looyengoed@… Owned by: anybody
Component: supplemental Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description

In the Windows time zone id <-> tz database time zone id mapping file "windowsZones.xml", there is one missing value in windows 10 version 1607. The Windows time zone id is "Kamchatka Standard Time" but is unmapped to a corresponding tzdatabase id.

In order to ensure correct mapping I believe the below line should be added. However, I am wondering if it's possible to have a duplicate territory? Not sure if this might break some rules.

<mapZone type="Asia/Kamchatka" territory="RU" other="Kamchatka Standard Time"/>

file: common/supplemental/windowsZones.xml

For added comparison, I can add the entire windows time zone id's list for Windows 1607 and attached to this report.

Attachments

WindowsZones1607.txt (3.1 KB) - added by robert.looyengoed@… 3 weeks ago.
List of all windows zone Ids in version 1607

Change History

Changed 3 weeks ago by robert.looyengoed@…

List of all windows zone Ids in version 1607

comment:1 Changed 12 days ago by yoshito

Windows zone - "Kamchatka Standard Time" is marked as obsolete. Our current policy is to exclude such zones from the mapping data.

There are a bunch of other zones previously available in Windows OS, but already obsolete. It looks Windows update does not delete registry keys for these obsolete zones, instead, mark them obsolete, so it does not show up in time zone selection UI.

comment:2 Changed 9 days ago by robert.looyengoed@…

That makes sense (it has 'Old' added to the display name in the English language). I also understand the simplicity of the current policy to exclude obsolete zones. However, it might be better to include old zones for compatibility if there is no technical reason against it.

There are a few different reasons for this:

  1. Accessing windows time zones from .net, there appears to be no indication of obsolete zones. I also can't seem to find Microsoft documentation on this to even determine it myself through the registry. You are correct that these are filtered from the windows OS time zone selection UI though so this information exists somewhere.
  1. In practice, many systems are not using the latest version of the OS. However, most software needs to work on several different versions of the OS. Without maintaining backwards compatibility in this list, windows developers using it are forced to put in their own table of exceptions. This kind of defeats the simplicity and use of CLDR here. I might as well just use my entire own lookup table for performance anyway.

I would be all for adding historical windows time zone ids all the way from Windows 7 to present. Perhaps these could also be marked as obsolete in the CLDR windowsZones.xml file with a new attribute. I'm sure many software projects would benefit from this.

View

Add a comment

Modify Ticket

Action
as new
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.