After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 699080 - No support for UTC and PDT
No support for UTC and PDT
Status: RESOLVED DUPLICATE of bug 692243
Product: gnome-clocks
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Clocks maintainer(s)
Clocks maintainer(s)
: 734971 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-04-27 21:18 UTC by Andreas Nilsson
Modified: 2014-09-02 19:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andreas Nilsson 2013-04-27 21:18:13 UTC
It's quite common that while working with people across timezones, you set a meeting time in UTC or PDT.
I frequently get called to meeting that are "11:00 PDT" and then I go like "shit, pretty sure I'm not going to be able to figure that one out".


1. http://en.wikipedia.org/wiki/Coordinated_Universal_Time
2. http://en.wikipedia.org/wiki/Pacific_Time_Zone
Comment 1 Matthias Clasen 2013-05-22 17:26:38 UTC
I would love this, too
Comment 2 Gergely POLONKAI 2014-03-30 08:01:45 UTC
Me either
Comment 3 Paolo Borelli 2014-08-19 07:10:08 UTC
*** Bug 734971 has been marked as a duplicate of this bug. ***
Comment 4 Paolo Borelli 2014-08-19 07:21:25 UTC
For the record, I would really like this too, right now this is blocked by the fact that we use libgweather location entry to add clocks, so we would not have any way to add it.

I'd like to have our own entry (maybe inline with a gtksearchentry + a listbox), but that is blocked by https://bugzilla.gnome.org/show_bug.cgi?id=734878
Comment 5 Michael Catanzaro 2014-08-19 14:05:19 UTC
FWIW there is nothing special about Pacific Daylight Time; it's just the timezone one hour behind Mountain Daylight Time and one hour ahead of Pacific Standard Time.  I'm not opposed to adding support for arbitrary timezones, distinct from any city, but you'd have to think about how to do this in a user-friendly way. We should not expect users to understand the distinction between PST and PDT, we should absolutely never display PST when we really mean PDT, and we probably can't automatically switch between the two because different countries (and Arizona...) switch timezones on different dates. In contrast, if you know PST/PDT is San Francisco or LA or Seattle, Clocks can just show you the right time without worry about complicated timezone nonsense.

But UTC is straightforward to handle, since that timezone is universally useful year-round.
Comment 6 Paolo Borelli 2014-09-02 19:59:13 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 692243 ***