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 649724 - translate monospace-font-name key to xsetting
translate monospace-font-name key to xsetting
Product: gnome-settings-daemon
Classification: Core
Component: xsettings
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-settings-daemon-maint
Depends on: 649721
Reported: 2011-05-08 11:01 UTC by Christian Persch
Modified: 2019-03-20 10:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

xsettings: Add monospace font name translation (1.36 KB, patch)
2011-05-08 11:01 UTC, Christian Persch
reviewed Details | Review

Description Christian Persch 2011-05-08 11:01:07 UTC
Translate the org.gnome.desktop.interface.monospace-font-name pref to Gtk/MonospaceFontName xsetting.
Comment 1 Christian Persch 2011-05-08 11:01:30 UTC
Created attachment 187451 [details] [review]
xsettings: Add monospace font name translation

Bug #649724.
Comment 2 Bastien Nocera 2011-05-16 23:46:27 UTC
Gtk/MonospaceFontName isn't mentioned in gtk+/gdk/x11/gdksettings.c
Comment 3 Christian Persch 2011-05-17 11:05:37 UTC
That's because it's not there yet; it comes from bug 649721 which is set as dependency below.
Comment 4 Bastien Nocera 2011-05-17 12:46:03 UTC
You have the dep the wrong way around then. I don't want gnome-settings-daemon producing warnings, so we'd need to bump the GTK+ version required.
Comment 5 Bastien Nocera 2013-06-05 10:05:35 UTC
Review of attachment 187451 [details] [review]:

The patch looks fine, but it needs the GTK+ patch merged before committing.
Comment 6 GNOME Infrastructure Team 2019-03-20 10:54:28 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: