<div dir="ltr">The CLDR project already does with its concept of "meta zones" which group together similar tz identifiers under a single, human-friendly name.</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, May 22, 2013 at 11:27 AM, <span dir="ltr"><<a href="mailto:random832@fastmail.us" target="_blank">random832@fastmail.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Or, more precisely, on the subject evicting redundant timezones from the<br>
user selection menu, since of course all current names will continue to<br>
exist as links if nothing else.<br>
<br>
I've thought about this some more, and I don't think it goes far enough.<br>
A user installing a new system doesn't _care_ about (my own proper time<br>
zone) America/Indianapolis, they don't have any need to accurately<br>
convert times from before _2006_ let alone 1970. Most users could<br>
probably be served just as well with America/New_York.<br>
<br>
I think it would be useful - particularly if we're abandoning being able<br>
to narrow it down by country - to define a heavily cut down set of<br>
"basic" time zones, that define each set of rules that exists _now_<br>
without care for maintaining the past back to 1970, and then offer an<br>
"advanced" option for the rest.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Random832<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Scott Atwood<br><br>
</div>