I agree that the solution is rather wanting, and believe that the timezone-guessing code is something that does not belong in any release. The idea of it not selecting a timezone at all is interesting: it would be very easy to do - I can make the patch if necessary - and wouldn't require any extra work.
However, I don't think upstream will accept that solution, whereas I think that having timezone data in the Locations.xml would be more likely to be accepted. If someone who has the ability to actually apply any of the patches here would give an opinion on what should be done, I would be happy to implement the code (though I certainly can't enter the timezone data!). -- 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
