I still believe the correct solution for hardy is to not infer a timezone based on the city coordinates at all, and instead fix the timezone selector. Trying to get correct timezone settings for all locations is going to take a lot of time and effort - relying on this means we will still have users for hardy who get the wrong tz suggestion.
-- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
