<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">In particular, in the current scenario, can we propose additions and corrections to the backzone file as new data becomes apparent, including adding new pre1970 zones?</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Galaxy</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: "Murray S. Kucherawy via tz" <tz@iana.org> </div><div>Date: 2021-09-22 15:16 (GMT-05:00) </div><div>To: Stephen Colebourne <scolebourne@joda.org> </div><div>Cc: Time Zone Mailing List <tz@iana.org> </div><div>Subject: Re: [tz] Issues with pre-1970 information in TZDB </div><div><br></div></div><div dir="ltr"><div dir="ltr">On Wed, Sep 22, 2021 at 3:52 AM Stephen Colebourne via tz <<a href="mailto:tz@iana.org">tz@iana.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Can we keep responses limited on this thread? Perhaps only respond if<br>
you think I've mischaracterized the issues at stake here? Or missed<br>
something obvious?<br></blockquote><div><br></div><div>My understanding is that these data are being moved from the regional files to the backzone file. It's been pointed out before that a compile-time option can be set to include those entries in the production output of the build.</div><div><br></div><div>If that's wrong or incomplete, please do correct me. In either case, can you please explain why that compile-time option is not an acceptable solution for those who object to the change?</div><div><br></div><div>-MSK<br></div></div></div>
</body></html>