From 4b0fd52e52968723ee2a415f0d2fae965aa96867 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Sat, 15 May 2010 18:23:23 -0400 Subject: [PATCH] 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 file 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. + + + 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 _summary + and _description elements in a + .gschema.xml.in file and use @INTLTOOL_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. GSettings is a bit more restrictive about key names than GConf. Key -- 2.7.4