luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-04-12 02:33:08 +02:00
Code Issues Packages Projects Releases Wiki Activity

Expand information about schema translation

Browse Source 
I have added some hints on how to use intltool for translation
of summary and description elements, taken from comments in bug #618523.
This commit is contained in:
Matthias Clasen 2010-05-15 18:23:23 -04:00
parent 2ad4b2d716
commit 4b0fd52e52
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -326,9 +326,19 @@ endif
will be used in similar ways by a future gsettings-editor, so you will be used in similar ways by a future gsettings-editor, so you
should use the same conventions for them: The summary is just a short should use the same conventions for them: The summary is just a short
label with no punctuation, the description can be one or more complete label with no punctuation, the description can be one or more complete
sentences. Translations for these strings will also be handled sentences.
</para>
<para>
Translations for these strings will also be handled
via gettext, so you should arrange for these strings to be via gettext, so you should arrange for these strings to be
extracted into your gettext catalog. 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_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.
</para> </para>
<para> <para>
GSettings is a bit more restrictive about key names than GConf. Key GSettings is a bit more restrictive about key names than GConf. Key