luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-26 05:56:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update GConf migration guide

Browse Source 
Newer intltool makes this much easier. Yay
https://bugzilla.gnome.org/show_bug.cgi?id=674620
This commit is contained in:
Matthias Clasen 2012-09-23 11:23:29 -04:00
parent 6270b3f384
commit 580b58c3c0
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/reference/gio/migrating-gconf.xml
View File

@ -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 <tag class="starttag">_summary</tag>
and <tag class="starttag">_description</tag> elements in a
.gschema.xml.in file and use
<literal>@<!-- -->INTLTOOL_XML_NOMERGE_RULE<!-- -->@</literal>
in your Makefile.am to produce the .gschema.xml file. The
<literal>NOMERGE</literal> 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 <filename>POTFILES.in</filename> with a line like
<programlisting>
[type: gettext/gsettings]data/org.foo.MyApp.gschema.xml
</programlisting>
</para>
<para>
GSettings is a bit more restrictive about key names than GConf. Key