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 696957 - Fahrenheit instead of celsius
Fahrenheit instead of celsius
Status: RESOLVED DUPLICATE of bug 695873
Product: gnome-weather
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Weather Maintainer(s)
GNOME Weather Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-03-31 11:53 UTC by Ignacio Casal Quinteiro (nacho)
Modified: 2013-04-02 14:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ignacio Casal Quinteiro (nacho) 2013-03-31 11:53:35 UTC 
I have the system in english although I changed the measurements in the gnome-control-center to the spanish ones. So this should mean the weather app should take celsius instead of fahrenheit.
Comment 1 Ignacio Casal Quinteiro (nacho) 2013-03-31 11:55:07 UTC 
I guess this is somehow fixed by:
https://git.gnome.org/browse/gnome-weather/commit/?id=2a7415ac1306d1390560e3fbcdd1f6376ef0affb

although I wonder if the system setting should take precedence...
Comment 2 Bruce Cowan 2013-03-31 19:31:01 UTC 
The libgweather translation should set the default units to use for each locale.
Comment 3 Ignacio Casal Quinteiro (nacho) 2013-03-31 20:51:18 UTC 
well... not so sure about that, I use the english language but I do want the spanish measurements and it is a valid option. that's why in gnome-control-center you can choose both settings
Comment 4 Matthias Clasen 2013-03-31 22:31:41 UTC 
the problem is likely that libgweather uses translated messages for this, meaning that it reacts to LC_MESSAGES, not LC_MEASUREMENT
Comment 5 Giovanni Campagna 2013-04-02 14:24:20 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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