I do want to point out that CLDR was required to have stable identifiers, so the identifiers it uses are frozen once entered for the first time in the TZ database. Formally it is not a problem for CLDR if the TZDB changes the 'canonical' TZ identifier in
zone.tab, as long as an alias is maintained to the old one. And even if the TZDB removes an alias, we will still keep an alias in CLDR for stability.<br><br>However, the more such changes are made, the more the 'canonical' identifiers will drift apart; so we'd prefer to see the changes minimized unless really necessary.
<br><br>Mark<br><br><div><span class="gmail_quote">On 7/24/06, <b class="gmail_sendername">Paul Eggert</b> <<a href="mailto:eggert@cs.ucla.edu">eggert@cs.ucla.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Chris Walton" <<a href="mailto:Chris.Walton@telus.com">Chris.Walton@telus.com</a>> writes:<br><br>> Should we:<br>> 1) update the entry for America/Coral_Harbour but not add a zone called America/Atikokan
<br>> Or<br>> 2) add a new zone for America/Atikoan and leave America/Coral_Harbour alone<br>> Or<br>> 3) delete America/Coral_Harbour, add America/Atikokan, and update the "zonetab" + "backward" files.
<br><br>I'm leaning toward #3. I don't recall seeing any other comments.<br></blockquote></div><br>