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

CLDR Ticket #11076(new data)

Opened 4 weeks ago

Last modified 13 days ago

metaZones.xml issues

Reported by: yoshito Owned by: anybody
Component: timezone Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


Description (last modified by roubert) (diff)

Copied from icubug:13691 reported by nfuller@…

I'm using ICU 60.2 for analyzing time zone data and I found a few anomalies that I wanted to check. This relates to Android: I'm using the name data to help when determining that two zones that are apparently identical (given offset transitions, offsets, etc.) are actually the same. I found a few cases where zones would be identical if not for the names and the ones below stood out as potentially being just incorrect name metadata data.

These may be from CLDR or may be ICU originated. Not sure.

ar : America/Argentina/San_Luis

"Western Argentina Standard Time" is the time zone for America/Argentina/San_Luis when should just be the same as all other Argentina zones? The rules are effectively identical.

cy : Asia/Famagusta

No name for Asia/Famagusta after ~2016-09-07T21:00:00Z?

                "1970-01-01 00:00",
                "2016-09-07 21:00",

kz : Asia/Aqtobe

metaZones.txt has a gap... 2004 -> 2005?

                "1970-01-01 00:00",
                "1991-12-15 19:00",
                "1991-12-15 19:00",
                "2004-10-30 21:00",
                "2005-10-30 21:00",
                "9999-12-31 23:59",

mn : Asia/Choibalsan

Asia/Choibalsan same as Asia/Ulaanbaatar after 2008-03-30T15:00:00Z but has a different name?

aq : Antarctica/Palmer

No name after 2016-12-04T03:00:00Z?




Change History

comment:1 Changed 13 days ago by roubert

  • Keywords android google added
  • Description modified (diff)

Add a comment

Modify Ticket

as new

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

Note: See TracTickets for help on using tickets.