From 580b58c3c0be3422c39925912e2282a917c96c8b Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Sun, 23 Sep 2012 11:23:29 -0400 Subject: [PATCH] Update GConf migration guide Newer intltool makes this much easier. Yay https://bugzilla.gnome.org/show_bug.cgi?id=674620 --- docs/reference/gio/migrating-gconf.xml | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/reference/gio/migrating-gconf.xml b/docs/reference/gio/migrating-gconf.xml index 44e4e32..413c10f 100644 --- a/docs/reference/gio/migrating-gconf.xml +++ b/docs/reference/gio/migrating-gconf.xml @@ -357,14 +357,12 @@ gsettings_SCHEMAS = my.app.gschema.xml Translations for these strings will also be handled via gettext, so you should arrange for these strings to be extracted into your gettext catalog. One way to do that is to use - intltool. For that, you use _summary - and _description elements in a - .gschema.xml.in file and use - @INTLTOOL_XML_NOMERGE_RULE@ - in your Makefile.am to produce the .gschema.xml file. The - NOMERGE part of the rule instructs intltool - to extract translatable strings, but not merge the translations - back into the generated xml file. + intltool. Since intltool 0.50.1, schema files are + supported, so all you have to do is to add your .gschema.xml + files to POTFILES.in with a line like + + [type: gettext/gsettings]data/org.foo.MyApp.gschema.xml + GSettings is a bit more restrictive about key names than GConf. Key -- 2.7.4