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

CLDR Ticket #5589(accepted data)

Opened 4 years ago

Last modified 18 months ago

America/Havana is missing from windowsZones.xml

Reported by: safkov@… Owned by: yoshito
Component: timezone Data Locale:
Phase: rc Review:
Weeks: Data Xpath:
Xref:

Description

America/Havana is not listed as unmappable on http://cldr.unicode.org/development/development-process/design-proposals/extended-windows-olson-zid-mapping yet it is missing from http://unicode.org/cldr/data/common/supplemental/windowsZones.xml.

Please either add America/Havana to windowsZones.xml or list it as unmappable.

Thank you.

Attachments

Change History

comment:1 Changed 4 years ago by yoshito

  • Owner changed from anybody to yoshito
  • Status changed from new to assigned
  • Type changed from defect to enhancement
  • Milestone changed from UNSCH to 23

America/Havana uses daylight saving time rule different from other countries in North America. Microsoft does not support Cuban time zone, so this zone cannot be 'reasonably' mappable to any Windows zone.

The design document referenced above is not maintained and mapping data is updated time to time. We could explicitly add unmappable Windows zones in windowsZones.xml.

comment:2 follow-up: ↓ 3 Changed 4 years ago by safkov@…

I like the idea of having a list of unmappable Windows time zones in windowsZones.xml.

I also think that having three categories (like in the design document) of Windows time zones makes sense:

  • mapped to equivalent
  • no DST rule equivalent
  • no base offset equivalent

That way Windows time zones missing from the mapping data could easily be pointed out.

Thank you.

comment:3 in reply to: ↑ 2 Changed 4 years ago by yoshito

  • Priority changed from assess to medium
  • Milestone changed from 23 to 24dres

Replying to safkov@…:

I like the idea of having a list of unmappable Windows time zones in windowsZones.xml.

I also think that having three categories (like in the design document) of Windows time zones makes sense:

  • mapped to equivalent
  • no DST rule equivalent
  • no base offset equivalent

That way Windows time zones missing from the mapping data could easily be pointed out.

I don't have time to add the new element for this purpose in CLDR 23 release. I'll work on this for CLDR 24.

comment:4 Changed 4 years ago by yoshito

  • Milestone changed from 24rc to 25dsub

Reviewed Windows TZ mapping data for CLDR 24. America/Havana with the latest update can be reasonably mapped to Eastern Standard Time (Cuba time only differs DST transition wall time, but they are same dates with US).

For explicitly specify unmappable with catetories - I need to update DTD and some tools. I'll revisit this for CLDR 25.

comment:5 Changed 3 years ago by emmons

  • Milestone changed from 25dsub to 25M1

Moving all 25dsub to 25M1. Please adjust the milestone if you are not planning to complete the item in the 25M1 time frame.

comment:6 Changed 3 years ago by yoshito

  • Milestone changed from 25M1 to 25rc

comment:7 follow-up: ↓ 8 Changed 3 years ago by mj1856@…

Is this really an acceptable mapping? The dates were completely out of alignment with the US between 2004 and 2012. and with the wall-time differences, it doesn't seem like a good match to me.

As far as I can tell, Cuba is currently unmappable.

comment:8 in reply to: ↑ 7 Changed 3 years ago by yoshito

  • Milestone changed from 25rc to 26rc

Replying to mj1856@…:

Is this really an acceptable mapping? The dates were completely out of alignment with the US between 2004 and 2012. and with the wall-time differences, it doesn't seem like a good match to me.

By the nature of Windows zone, it does not support historic changes before 2006. Also, Microsoft tries to group multiple locations in a zone. Therefore, it's not possible to create mapping data including historic differences for many places. As far as I know, consumer of the data care about 'current' mapping. The goal of the data in CLDR is to provide better coverage for the mapping based on the latest rules.

As far as I can tell, Cuba is currently unmappable.

I'm not trying to provide a mapping data for America/Havana. I keep this ticket open for adding a way to describe unmappable zones.

comment:9 Changed 3 years ago by yoshito

  • Milestone changed from 26rc to 27dsub

comment:10 Changed 3 years ago by markus

  • Phase set to dsub
  • Milestone changed from 27dsub to 27

comment:11 Changed 2 years ago by emmons

  • Milestone changed from 27 to 28

comment:12 Changed 2 years ago by yoshito

  • Phase changed from dsub to rc

Reviewed this ticket on 2015-04-15 again. We already have America/Havana in the mapping data, but we still don't have "unmappable" zones not included in the windowsZones.xml. I'll keep this ticket for the task.

comment:13 Changed 2 years ago by markus

  • Type changed from enhancement to data

comment:14 Changed 2 years ago by srl

  • Status changed from assigned to accepted

comment:15 Changed 18 months ago by emmons

  • Milestone changed from 28 to 28roll

Moving all outstanding 28 tickets to 28roll. We will discuss disposition of these at the next CLDR TC.

View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.