On 08/15/2012 12:23 PM, John Hawkinson wrote:
Could we please move UI improvements out of the TZ project? There's just not clear concensus that we should.
The reality is that, despite what implementors allegedly *should* do, users frequently do encounter tz identifiers. This is manifestly true, otherwise we would not hear so many complaints about it.
I completely agree. For 99% of timezones, we have a link that works, and that can be presented to the user in time zone picker apps (even if it's not supposed to). This breaks* for one timezone, and it just so happens that that timezone is probably the most populous in the entire database. My motivation is a little selfish in that this one line change will make any changes to time zone picker apps unnecessary. But by not taking that we're necessitating many man-hours of work for UI changes for all the apps that currently use zone.tab. I agree, zone.tab is _not_ good for presenting human-readable names, but the truth is, it's also not _bad_. * Where "breaks" in this case means that the timezone as used in casual speech is named after a city, one that's not in the zone.tab already, and users are so confused with the name of their zone in zone.tab that they actually think it's wrong and their timezone is just missing.