[glib] Expand information about schema translation



commit 4b0fd52e52968723ee2a415f0d2fae965aa96867
Author: Matthias Clasen <mclasen redhat com>
Date:   Sat May 15 18:23:23 2010 -0400

    Expand information about schema translation
    
    I have added some hints on how to use intltool for translation
    of summary and description elements, taken from comments in bug #618523.

 docs/reference/gio/migrating-gconf.xml |   14 ++++++++++++--
 1 files changed, 12 insertions(+), 2 deletions(-)
---
diff --git a/docs/reference/gio/migrating-gconf.xml b/docs/reference/gio/migrating-gconf.xml
index 23c2ddb..14290f4 100644
--- a/docs/reference/gio/migrating-gconf.xml
+++ b/docs/reference/gio/migrating-gconf.xml
@@ -326,9 +326,19 @@ endif
         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
         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
-        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>
         GSettings is a bit more restrictive about key names than GConf. Key



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]