Bug#509745: tzdata: Please restore US timezone configurations.
On Thu, Dec 25, 2008 at 12:19:45PM -0600, Bob Proulx wrote:
> are much smaller, and that is not really what is needed. Quick, what
> is the correct city to choose to select US Central Standard Time when
> in KC? I see Winnipeg in the list and the web shows me that it is in
> the same timezone so I guess Winnipeg is the best choice for me in KC.
Assuming this isn't rhetorical, the answer is America/Chicago.
> Previously I could simply choose US Central Standard Time in order to
> set the timezone to US Central Time.
> Restoring the ability to choose the timezone by timezone name is
> exactly what is needed. Thanks.
I agree that it would be beneficial to make some changes with the
timezone selection UI, but I don't think anyone has a fully-formed
plan on how to achieve this. At this point, even if we did, it
wouldn't make it into lenny.
The squeeze solution needs to be translated into at least 30
languages and inclusive of all 428 or however many real upstream
timezones there will be at the time. Note that even though
the US zones are far easier for Americans to deal with, they are
just backward-compatibility links to America/Anchorage,
America/Adak, America/Phoenix, America/Chicago,
America/Indiana/Indianapolis, America/New_York, Pacific/Honolulu,
America/Indiana/Knox, America/Detroit, America/Denver,
America/Los_Angeles, Pacific/Pago_Pago. There is another gentleman
who wants us to refrain from presenting "America" to the end user
on the grounds that it is grammatically incorrect.
We can go with what we have now and just special-case the US
compatibility zones, but I think there's probably a better way.
Reply to: