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

CLDR Ticket #6971(closed: as-designed)

Opened 5 years ago

Last modified 5 years ago

Additional Windows Zone Mappings

Reported by: mj1856@… Owned by: yoshito
Component: other-supplemental Data Locale:
Phase: Review:
Weeks: Data Xpath:


Please consider the following additions to the supplemental Windows time zone mappings. Thank you.

  • Asia/Ho_Chi_Minh => SE Asia Standard Time
  • Asia/Kolkata => India Standard Time
  • Africa/Asmara => E. Africa Standard Time
  • Asia/Kathmandu => Nepal Standard Time
  • Atlantic/Faroe => GMT Standard Time
  • Pacific/Chuuk => West Pacific Standard Time
  • Pacific/Pohnpei => Central Pacific Standard Time
  • America/Argentina/Buenos_Aires => Argentina Standard Time
  • America/Argentina/Catamarca => Argentina Standard Time
  • America/Argentina/Cordoba => Argentina Standard Time
  • America/Argentina/Jujuy => Argentina Standard Time
  • America/Argentina/Mendoza => Argentina Standard Time
  • America/Indiana/Indianapolis => US Eastern Standard Time
  • America/Kentucky/Louisville => Eastern Standard Time


Change History

comment:1 Changed 5 years ago by emmons

  • Owner changed from anybody to yoshito
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 25rc

comment:2 Changed 5 years ago by yoshito

  • Status changed from assigned to closed
  • Resolution set to as-designed

CLDR defines canonical time zone IDs and the mapping is defined in timezone.xml. CLDR project needs stable time zone IDs that won't change time to time. When the time zone database adds a new ID (for example, Asia/Ho_Chi_Minh) replacing an old ID by moving it to backward file (for example, Asia/Saigon), CLDR still uses the old ID as the canonical ID, but define the mapping in timezone.xml.

For example, the data below in timezone.xml:

<type name="vnsgn" description="Ho Chi Minh City, Vietnam" alias="Asia/Saigon Asia/Ho_Chi_Minh"/>

In the line above, alias attribute may contain multiple zone IDs. When multiple entries are found in the attribute, the first one is the 'long' canonical ID used by CLDR and the rest are equivalent 'long' IDs. All of CLDR locale data (for example, localized names) uses "Asia/Saigon" as the key.

All of these zone IDs reported in this ticket are 'new' IDs replacing 'old' IDs currently found in backward file in the tz database, and timezone.xml in CLDR. CLDR does not want to duplicate mappings for both new and old IDs.

So, this is as designed. The consumer of CLDR data should use timezone.xml to canonicalize zone ID first, then use the mapping data in windowsZones.xml.

comment:3 Changed 5 years ago by mj1856@…

Thank you for the clarification.

comment:4 Changed 5 years ago by emmons

  • Milestone 25rc deleted

Milestone 25rc deleted


Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

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

Note: See TracTickets for help on using tickets.