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 66556 - user-font doesn't work.
user-font doesn't work.
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
1.4.0
Other Linux
: Normal normal
: 1.4.1
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-12-09 14:11 UTC by Akira TAGOH
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
I have a patch (723 bytes, patch)
2001-12-09 14:11 UTC, Akira TAGOH 		none Details | Review

Description Akira TAGOH 2001-12-09 14:11:04 UTC 
When specified user-font by theme-selector-capplet, theme-selector-capplet
have generated 'font' in .gtkrc. but GTK+ already has 'fontset' in
/etc/gtk/gtkrc*, and GTK+ gives priority to 'fontset' over 'font'. so that
GTK+ has ignored user-font in .gtkrc.

theme-selector-capplet should be generate 'fontset' instead of 'font'.
Comment 1 Akira TAGOH 2001-12-09 14:11:51 UTC 
Created attachment 6191 [details] [review]
I have a patch
Comment 2 Simos Xenitellis 2001-12-26 17:07:07 UTC 
Possibly related with Bug 62682
(http://bugzilla.gnome.org/show_bug.cgi?id=62682)

I cannot understand why it affects specific locales only.
The problematic locales are not only the non-(iso-8859-1) locales.
Comment 3 Akira TAGOH 2001-12-26 22:48:32 UTC 
GTK+ doesn't have gtkrc for iso-8859-1 ONLY by default. it means even
if current theme-selector-capplet set an user font by 'font', it will
works.
Also for locates without iso-8859-1, if didn't generate those locales
correctly by localedef or specified the locales which nothing is, it
will also works since glibc handle as same locale C.
Comment 4 Kjartan Maraas 2002-01-20 16:07:03 UTC 
Commited. Thanks.