Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Editorial: Handle case when backzone doesn't contain link
A couple of links aren't in `backzone`. Change the assertion to an if-step to correctly handle this case. List of time zones which weren't correctly handled: ``` Africa/Kinshasa Africa/Lubumbashi America/Atikokan America/Blanc-Sablon America/Creston Antarctica/DumontDUrville Antarctica/McMurdo Antarctica/Syowa Asia/Kuala_Lumpur Europe/Busingen Pacific/Chuuk Pacific/Majuro Pacific/Midway Pacific/Pohnpei Pacific/Wake ``` For example "Africa/Kinshasa", which is a zone in `backzone`: - "Africa/Kinshasa" is a link to "Africa/Lagos" per `backward`. - The region code for "Africa/Lagos" is "NG", the region code for "Africa/Kinshasa" is "CD". That means the condition in step 5.b.iii.3 evaluates to false. - There are two entries for the region "CD" in `zone.tab`: "Africa/Kinshasa" and "Africa/Lubumbashi". That means the condition in step 5.b.iii.4.b also evaluates to false. - "Africa/Kinshasa" is a zone in `backzone`, so the loop in step 5.b.iii.4.c.iii won't find any entries. All other cases are also zones in `backzone`, except for "Europe/Busingen", which is always a link. "Europe/Busingen" links to "Europe/Zurich" per `backward`, but is still a primary identifier in ECMA-402, because Büsingen is politically a part of Germany, so it shouldn't be merged with the time zone for Zürich (Switzerland).
- Loading branch information