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 622190 - Keyboard indicator doesn't honor font antialiasing settings
Keyboard indicator doesn't honor font antialiasing settings
Status: RESOLVED INCOMPLETE
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2010-06-20 13:09 UTC by a937923
Modified: 2010-10-19 18:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
two notification area screenshots (3.07 KB, image/png)
2010-06-20 13:18 UTC, a937923
Details

Description a937923 2010-06-20 13:09:04 UTC
Even if antialiasing is turned off, either via gnome-appearance-properties or via /etc/fonts/*, GNOME 2.30 keyboard indicator in notification area does render antialiased text. Mysteriously, this happens only for particular layouts. In my case (see attachment), the "США" text (meaning "US" in Russian) is antialiased, while "Рус" ("Rus") is not. I've noticed that almost all three-letter abbreviations are rendered correctly, without antialiasing (except that "США" one), while four-letter ones are antialiased unconditionally. Seems like antialiasing here is the result of horizontal scaling when the resulting text doesn't fit some certain pixel width.

I'm using Mandriva 2010.1 (Cooker), ru_RU locale, Tahoma font.
Comment 1 a937923 2010-06-20 13:18:59 UTC
Created attachment 164139 [details]
two notification area screenshots
Comment 2 Sergey V. Udaltsov 2010-07-01 20:30:48 UTC
I suspect the issue with cairo rendering. In libgnomekbd, check the file libgnomekbd/gkbd-status.c. On line 357, there is #ifdef 0. Change it to #ifdef 1 and rebuild libgnomekbd. After you restart g-s-d, you will get the files label0.png and label1.png. Please attach them here. I suspect the defects are visible in those files.
If so, it is between libgnomekbd and cairo.

What you also can try is

cairo_font_options_set_antialias (fo, CAIRO_ANTIALIAS_NONE);

on line 211 (before pango_cairo_set_font_options).

Check if will change the behavior.
Comment 3 Felipe Besoaín Pino 2010-10-19 18:19:45 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!