Remove generic metazone values that match location values

[robertbastian]

-100KB

Generic non-location format ("Central European Time", "Armenia Time") falls back to location ("Zurich Time", "Armenia Time"), so we can remove duplicates.

There are some entries that I feel should be deduplicated, but aren't (metazone name listed first):

• The metazone name is more specific than the location name. This is weird, because for the location format, the region should be used if there's only one time zone in the country. We do this, but then the metazone exists and reverts that
  • Apia Time vs Samoa Time
  • Pyongyang Time vs North Korea Time
  • Taipei Time vs Taiwan Time
  • Petropavlovsk-Kamchatski Time vs Kamchatka Time
• The generic meta zone includes "standard". This is a data issue, the problem is probably that for non-DST metazones, the only entry is standard, which might confuse linguists:
  • Guam Standard Time vs Guam Time
  • Singapore Standard Time vs Singapore Time
• The match is not perfect. Some of this data definitely needs to be cleaned up, but others might be fixed by using a different region display name in datagen.
  • Brunei Darussalam Time vs Brunei Time
  • Cocos Islands Time vs Cocos (Keeling) Islands Time
  • Dumont-d’Urville Time vs Dumont d’Urville Time
  • East Timor Time vs Timor-Leste Time
  • Easter Island Time vs Easter Time
  • Fernando de Noronha Time vs Noronha Time
  • French Southern & Antarctic Time vs French Southern Territories Time
  • Hong Kong Time vs Hong Kong SAR China Time
  • Indian Ocean Time vs British Indian Ocean Territory Time
  • Lanka Time vs Sri Lanka Time
  • Macao Time vs Macao SAR China Time
  • Myanmar Time vs Myanmar (Burma) Time
  • North Mariana Islands Time vs Northern Mariana Islands Time
  • Philippine Time vs Philippines Time
  • Pitcairn Time vs Pitcairn Islands Time
  • Ponape Time vs Pohnpei Time
  • South Georgia Time vs South Georgia & South Sandwich Islands Time
  • Wake Island Time vs Wake Time

[Manishearth]

code seems fine but I'm not fully clear on the implications of this, defer to @sffc or other tz reviewers

[sffc]

Singapore Standard Time vs Singapore Time

Wikipedia says both names are valid: https://en.wikipedia.org/wiki/Singapore_Time

In general I think it's probably safest to only deduplicate in cases of an exact match, as much as I'd like to be more aggressive, and then discuss this list with CLDR to find more opportunities for deduplication.

[sffc]

Hong Kong SAR China Time
Myanmar (Burma) Time

These look pretty silly, raising questions about whether we want a Location format to ever be chosen, and instead push people toward an improved Generic Non-Location that supports Generic Partial Location.

[sffc]

Issue: Can you cite the algorithm where we want short names? I assume you did it maybe to normalize "Myanmar (Burma)" to "Myanmar" and things like that, but normalizing "United Kingdom" to "UK" might not be desirable?

[robertbastian]

UTS-35 does not specify which names to use. I think UK Time is better than United Kingdom Time, because it is shorter.

[robertbastian]

These look pretty silly

Well they are Hong Kong Time and Macao Time as of the latest commit.

[robertbastian]

In general I think it's probably safest to only deduplicate in cases of an exact match, as much as I'd like to be more aggressive, and then discuss this list with CLDR to find more opportunities for deduplication.

That's what I'm doing. These are observations that we need to bring to CLDR.

[sffc]

Let's make a CLDR issue to discuss with the CLDR Design WG, both the short vs long location names and the other issues you found.

[robertbastian]

• CLDR-18075
• CLDR-18076
• CLDR-18077
• CLDR-18078