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 526437 - Avoid combo characters for degrees-C/F
Avoid combo characters for degrees-C/F
Status: RESOLVED FIXED
Product: libgweather
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: 2.22.0
Assigned To: libgweather-maint
libgweather-maint
: 541340 547082 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-06 03:19 UTC by Owen Taylor
Modified: 2009-01-27 14:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Owen Taylor 2008-04-06 03:19:48 UTC
Right now GWeather does:

  g_snprintf(buf, sizeof (buf), _("%d \342\204\211"), (int)floor(far + 0.5));

(4 instances, 2 for each of degrees-C and degrees-F)

The problem is that these characters are rare and and don't appear
in many fonts, so you'll get random fallbacks to whatever has the character
on the system.

It would be better to use the degrees-character + a C or an F. If a font
wants to improve the kerning on that pair or the placement of the degrees
sign, we have the technology to do it properly in the GNOME desktop.

Unfortunately these strings are in the .po files. I think the right thing
to do is to do a search-and-replace across the PO files for the degrees-C
and degrees-F characters and replace them there. There are almost no real
translations for these (just he and ar for fahrenheit, for example) and
the translations that are there a affected properly by that replacement.
Comment 1 Pacho Ramos 2008-08-31 11:27:10 UTC
I am also suffering this on my system as I don't use liberation-fonts
Comment 2 Josselin Mouette 2008-09-04 09:42:51 UTC
Confirming. See also http://bugs.debian.org/486523
Comment 3 Dan Winship 2008-11-25 15:29:30 UTC
fixed in trunk

(In reply to comment #0)
> Unfortunately these strings are in the .po files. I think the right thing
> to do is to do a search-and-replace across the PO files for the degrees-C
> and degrees-F characters and replace them there.

This actually ended up causing problems, because most of the .po files already had the string with separate degree and C/F as well, as an unused translation (presumably leftover from gweather-applet?), and so fixing the existing translation created a duplicate, which then caused the pre-commit check to fail. So I've just left the po files untouched for now, and when they next update, it should pick up the old translation automatically.
Comment 4 Dan Winship 2009-01-27 14:46:22 UTC
*** Bug 541340 has been marked as a duplicate of this bug. ***
Comment 5 Dan Winship 2009-01-27 14:47:06 UTC
*** Bug 547082 has been marked as a duplicate of this bug. ***