Update to canonical names

[mattjohnsonpint]

One of my users pointed out that my library is returning Asia/Rangoon instead of Asia/Yangon for locations in Myanmar. mattjohnsonpint/GeoTimeZone#28

This appears to stem from the data in the timezones.json file here.

Could you please check that the time zone ids are all canoncialized to the current Zone entries instead of Link entries?

Thanks.

[evansiroky]

Will do. Thanks for bringing this to my attention. So basically I should refactor any zone that appears in the 3rd column of the backward file of the timezone database, right?

[mattjohnsonpint]

Really, just any Link entry, regardless of which file its found in. There are several links that are in the region files.

Sure, any consumer could resolve the link themselves, so it's not super critical - but there's no reason not to give the canonical Zone name.

[evansiroky]

Hmm, I looked at this a bit further and you're right that there are a bunch of links in the regions files.
Since the timezone database tries to have a zone for each nation-state I'm kind of leaning toward keeping those linked zone names in this project.

The backward zones I'll definitely fix tho. Here's a running list of my progress on refactoring them.

• America/Atikokan
• America/Coral_Harbour
• America/Montreal
• America/Toronto
• Asia/Chongqing
• Asia/Harbin
• Asia/Kashgar
• Asia/Rangoon
• Asia/Shanghai
• Asia/Urumqi
• Asia/Yangon
• Pacific/Chuuk
• Pacific/Honolulu
• Pacific/Johnston
• Pacific/Yap

[mattjohnsonpint]

Sure. If the only entry for a given nation-state is a link to a zone that is in a different nation-state, then use the link. Otherwise, use the zone. That makes sense.