RubyGems - pango - Versions diffs - 0.90.5-x86-mingw32 → 0.90.6-x86-mingw32 - Mend

pango 0.90.5-x86-mingw32 → 0.90.6-x86-mingw32

Files changed (1348) hide show

data/vendor/local/share/gtk-doc/html/gio/ch26s03.html DELETED

@@ -1,159 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>GConfClient (and GConfBridge) API conversion</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="ch26.html" title="Migrating from GConf to GSettings">
-<link rel="prev" href="ch26s02.html" title="Conceptual differences">
-<link rel="next" href="ch26s04.html" title="Change notification">
-<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="ch26s02.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="ch26.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">GIO Reference Manual</th>
-<td><a accesskey="n" href="ch26s04.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="section">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id618463"></a>GConfClient (and GConfBridge) API conversion</h2></div></div></div>
-<p>
-        Most people use GConf via the high-level <span class="type">GConfClient</span> API.
-        The corresponding API is the <a class="link" href="GSettings.html" title="GSettings"><span class="type">GSettings</span></a> object. While not
-        every GConfClient function has a direct GSettings equivalent,
-        many do:
-        </p>
-<div class="table">
-<a name="gconf-client-vs-gsettings"></a><p class="title"><b>Table 6. </b></p>
-<div class="table-contents"><table border="1">
-<colgroup>
-<col>
-<col>
-</colgroup>
-<thead><tr>
-<th>GConfClient</th>
-<th>GSettings</th>
-</tr></thead>
-<tbody>
-<tr>
-<td><code class="function">gconf_client_get_default()</code></td>
-<td>no direct equivalent,
-                                                                   instead you call <a class="link" href="GSettings.html#g-settings-new" title="g_settings_new ()"><code class="function">g_settings_new()</code></a> for the schemas you use</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set" title="g_settings_set ()"><code class="function">g_settings_set()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get" title="g_settings_get ()"><code class="function">g_settings_get()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_bool()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-boolean" title="g_settings_get_boolean ()"><code class="function">g_settings_get_boolean()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_bool()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-boolean" title="g_settings_set_boolean ()"><code class="function">g_settings_set_boolean()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_int()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-int" title="g_settings_get_int ()"><code class="function">g_settings_get_int()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_int()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-int" title="g_settings_set_int ()"><code class="function">g_settings_set_int()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_float()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-double" title="g_settings_get_double ()"><code class="function">g_settings_get_double()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_float()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-double" title="g_settings_set_double ()"><code class="function">g_settings_set_double()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_string()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-string" title="g_settings_get_string ()"><code class="function">g_settings_get_string()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_string()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-string" title="g_settings_set_string ()"><code class="function">g_settings_set_string()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_list()</code></td>
-<td>for string lists, see <a class="link" href="GSettings.html#g-settings-get-strv" title="g_settings_get_strv ()"><code class="function">g_settings_get_strv()</code></a>, else see <a class="link" href="GSettings.html#g-settings-get-value" title="g_settings_get_value ()"><code class="function">g_settings_get_value()</code></a> and <a href="http://library.gnome.org/devel/glib/unstable/glib-GVariant.html#GVariant"><span class="type">GVariant</span></a> API</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_list()</code></td>
-<td>for string lists, see <a class="link" href="GSettings.html#g-settings-set-strv" title="g_settings_set_strv ()"><code class="function">g_settings_set_strv()</code></a>, else see <a class="link" href="GSettings.html#g-settings-set-value" title="g_settings_set_value ()"><code class="function">g_settings_set_value()</code></a> and <a href="http://library.gnome.org/devel/glib/unstable/glib-GVariant.html#GVariant"><span class="type">GVariant</span></a> API</td>
-</tr>
-<tr>
-<td><code class="function">gconf_entry_get_is_writable()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-is-writable" title="g_settings_is_writable ()"><code class="function">g_settings_is_writable()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_notify_add()</code></td>
-<td>not required, the <a class="link" href="GSettings.html#GSettings-changed" title='The "changed" signal'><span class="type">"changed"</span></a> signal is emitted automatically</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_add_dir()</code></td>
-<td>not required, each GSettings instance automatically watches all keys in its path</td>
-</tr>
-<tr>
-<td><span class="type">GConfChangeSet</span></td>
-<td>
-<a class="link" href="GSettings.html#g-settings-delay" title="g_settings_delay ()"><code class="function">g_settings_delay()</code></a>, <a class="link" href="GSettings.html#g-settings-apply" title="g_settings_apply ()"><code class="function">g_settings_apply()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_default_from_schema()</code></td>
-<td>no equivalent, applications are expected to know their schema</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_all_entries()</code></td>
-<td>no equivalent, applications are expected to know their schema, and GSettings does not allow schema-less entries</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_without_default()</code></td>
-<td>no equivalent</td>
-</tr>
-<tr>
-<td><code class="function">gconf_bridge_bind_property()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-bind" title="g_settings_bind ()"><code class="function">g_settings_bind()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_bridge_bind_property_full()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-bind-with-mapping" title="g_settings_bind_with_mapping ()"><code class="function">g_settings_bind_with_mapping()</code></a></td>
-</tr>
-</tbody>
-</table></div>
-</div>
-<p><br class="table-break">
-      </p>
-<p>
-        GConfBridge was a third-party library that used GConf to bind an object property
-        to a particular configuration key. GSettings offers this service itself.
-      </p>
-<p>
-        There is a pattern that is sometimes used for GConf, where a setting can have
-        explicit 'value A', explicit 'value B' or 'use the system default'. With GConf,
-        'use the system default' is sometimes implemented by unsetting the user value.
-      </p>
-<p>
-        This is not possible in GSettings, since it does not have API to determine if a value
-        is the default and does not let you unset values. The recommended way (and much
-        clearer) way in which this can be implemented in GSettings is to have a separate
-        'use-system-default' boolean setting.
-      </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gio/ch26s04.html DELETED

@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Change notification</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="ch26.html" title="Migrating from GConf to GSettings">
-<link rel="prev" href="ch26s03.html" title="GConfClient (and GConfBridge) API conversion">
-<link rel="next" href="ch26s05.html" title="Change sets">
-<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="ch26s03.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="ch26.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">GIO Reference Manual</th>
-<td><a accesskey="n" href="ch26s05.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="section">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id386027"></a>Change notification</h2></div></div></div>
-<p>
-        GConf requires you to call <code class="function">gconf_client_add_dir()</code> and
-        <code class="function">gconf_client_notify_add()</code> to get change notification. With
-        GSettings, this is not necessary; signals get emitted automatically
-        for every change.
-      </p>
-<p>
-        The <a class="link" href="GSettings.html#GSettings-changed" title='The "changed" signal'><span class="type">"changed"</span></a> signal is emitted for each changed key.
-        There is also a <a class="link" href="GSettings.html#GSettings-change-event" title='The "change-event" signal'><span class="type">"change-event"</span></a> signal that you can handle
-        if you need to see groups of keys that get changed at the same time.
-      </p>
-<p>
-        GSettings also notifies you about changes in writability of keys,
-        with the <a class="link" href="GSettings.html#GSettings-writable-changed" title='The "writable-changed" signal'><span class="type">"writable-changed"</span></a> signal (and the
-        <a class="link" href="GSettings.html#GSettings-writable-change-event" title='The "writable-change-event" signal'><span class="type">"writable-change-event"</span></a> signal).
-      </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gio/ch26s05.html DELETED

@@ -1,48 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Change sets</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="ch26.html" title="Migrating from GConf to GSettings">
-<link rel="prev" href="ch26s04.html" title="Change notification">
-<link rel="next" href="ch26s06.html" title="Schema conversion">
-<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="ch26s04.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="ch26.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">GIO Reference Manual</th>
-<td><a accesskey="n" href="ch26s06.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="section">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id584764"></a>Change sets</h2></div></div></div>
-<p>
-        GConf has a a concept of a set of changes which can be applied or reverted
-        at once: <span class="type">GConfChangeSet</span> (GConf doesn't actually apply changes atomically,
-        which is one of its shortcomings).
-      </p>
-<p>
-        Instead of a separate object to represent a change set, GSettings has a
-        'delayed-apply' mode, which can be turned on for a GSettings object by
-        calling <a class="link" href="GSettings.html#g-settings-delay" title="g_settings_delay ()"><code class="function">g_settings_delay()</code></a>. In this mode, changes done to the GSettings
-        object are not applied - they are still visible when calling <a class="link" href="GSettings.html#g-settings-get" title="g_settings_get ()"><code class="function">g_settings_get()</code></a>
-        <span class="emphasis"><em>on the same object</em></span>, but not to other GSettings instances
-        or even other processes.
-      </p>
-<p>
-        To apply the pending changes all at once (GSettings <span class="emphasis"><em>does</em></span>
-        atomicity here), call <a class="link" href="GSettings.html#g-settings-apply" title="g_settings_apply ()"><code class="function">g_settings_apply()</code></a>. To revert the pending changes,
-        call <a class="link" href="GSettings.html#g-settings-revert" title="g_settings_revert ()"><code class="function">g_settings_revert()</code></a> or just drop the reference to the <a class="link" href="GSettings.html" title="GSettings"><span class="type">GSettings</span></a> object.
-      </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gio/ch26s06.html DELETED

@@ -1,277 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Schema conversion</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="ch26.html" title="Migrating from GConf to GSettings">
-<link rel="prev" href="ch26s05.html" title="Change sets">
-<link rel="next" href="ch26s07.html" title="Data conversion">
-<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="ch26s05.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="ch26.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">GIO Reference Manual</th>
-<td><a accesskey="n" href="ch26s07.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="section">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id536353"></a>Schema conversion</h2></div></div></div>
-<p>
-        If you are porting your application from GConf, most likely you already
-        have a GConf schema. GConf comes with a commandline tool
-        gsettings-schema-convert
-        that can help with the task of converting a GConf schema into
-        an equivalent GSettings schema. The tool is not perfect and
-        may need assistence in some cases.
-      </p>
-<div class="example">
-<a name="id490225"></a><p class="title"><b>Example 13. An example for using gsettings-schema-convert</b></p>
-<div class="example-contents">
-<p>Running <strong class="userinput"><code>gsettings-schema-convert --gconf --xml --schema-id "org.gnome.font-rendering" --output org.gnome.font-rendering.gschema.xml destop_gnome_font_rendering.schemas</code></strong> on the following <code class="filename">desktop_gnome_font_rendering.schemas</code> file:
-        </p>
-<pre class="programlisting">
-&lt;?xml version="1.0"?&gt;
-&lt;gconfschemafile&gt;
-    &lt;schemalist&gt;
-        &lt;schema&gt;
-            &lt;key&gt;/schemas/desktop/gnome/font_rendering/dpi&lt;/key&gt;
-            &lt;applyto&gt;/desktop/gnome/font_rendering/dpi&lt;/applyto&gt;
-            &lt;owner&gt;gnome&lt;/owner&gt;
-            &lt;type&gt;int&lt;/type&gt;
-            &lt;default&gt;96&lt;/default&gt;
-            &lt;locale name="C"&gt;
-                &lt;short&gt;DPI&lt;/short&gt;
-                &lt;long&gt;The resolution used for converting font sizes to pixel sizes, in dots per inch.&lt;/long&gt;
-            &lt;/locale&gt;
-        &lt;/schema&gt;
-    &lt;/schemalist&gt;
-&lt;/gconfschemafile&gt;
-</pre>
-<p>
-produces a <code class="filename">org.gnome.font-rendering.gschema.xml</code> file with the following content:
-</p>
-<pre class="programlisting">
-&lt;schemalist&gt;
-  &lt;schema id="org.gnome.font-rendering" path="/desktop/gnome/font_rendering/"&gt;
-    &lt;key name="dpi" type="i"&gt;
-      &lt;default&gt;96&lt;/default&gt;
-      &lt;summary&gt;DPI&lt;/summary&gt;
-      &lt;description&gt;The resolution used for converting font sizes to pixel sizes, in dots per inch.&lt;/description&gt;
-    &lt;/key&gt;
-  &lt;/schema&gt;
-&lt;/schemalist&gt;
-</pre>
-<p>
-</p>
-</div>
-</div>
-<br class="example-break"><p>
-        GSettings schemas are identified at runtime by their id (as specified
-        in the XML source file). It is recommended to use a dotted name as schema
-        id, similar in style to a DBus bus name, e.g. "org.gnome.font-rendering".
-       The filename used for the XML schema source is immaterial, but
-       schema compiler expects the files to have the extension
-       <code class="filename">.gschema.xml</code>. It is recommended to simply
-       use the schema id as the filename, followed by this extension,
-       e.g. <code class="filename">org.gnome.font-rendering.gschema.xml</code>.
-      </p>
-<p>
-        The XML source file for your GSettings schema needs to get installed
-        into <code class="filename">$datadir/glib-2.0/schemas</code>, and needs to be
-        compiled into a binary form. At runtime, GSettings looks for compiled
-        schemas in the <code class="filename">glib-2.0/schemas</code> subdirectories
-        of all <code class="envar">XDG_DATA_DIRS</code> directories, so if you install
-        your schema in a different location, you need to set the
-        <code class="envar">XDG_DATA_DIRS</code> environment variable appropriately.
-      </p>
-<p>
-        Schemas are compiled into binary form by the
-        <a href="glib-compile-schemas.html">glib-compile-schemas</a> utility.
-        GIO provides a <code class="literal">glib_compile_schemas</code>
-        variable for the schema compiler.
-      </p>
-<p>
-        You can ignore all of this by using the provided m4 macros.  To
-        do this, add to your <code class="filename">configure.ac</code>:
-</p>
-<pre class="programlisting">
-GLIB_GSETTINGS
-</pre>
-<p>
-        The corresponding <code class="filename">Makefile.am</code> fragment looks like
-        this:
-</p>
-<pre class="programlisting">
-# gsettings_SCHEMAS is a list of all the schemas you want to install
-gsettings_SCHEMAS = my.app.gschema.xml
-# include the appropriate makefile rules for schema handling
-@GSETTINGS_RULES@
-</pre>
-<p>
-      </p>
-<p>
-        This is not sufficient on its own.  You need to mention what the source
-        of the <code class="filename">my.app.gschema.xml</code> file is.  If the schema
-        file is distributed directly with your project's tarball then a mention
-        in <code class="varname">EXTRA_DIST</code> is appropriate.  If the schema file is
-        generated from another source then you will need the appropriate rule
-        for that, plus probably an item in <code class="varname">EXTRA_DIST</code> for the
-        source files used by that rule.
-      </p>
-<p>
-        One possible pitfall in doing schema conversion is that the default
-        values in GSettings schemas are parsed by the <a href="http://library.gnome.org/devel/glib/unstable/glib-GVariant.html#GVariant"><span class="type">GVariant</span></a> parser.
-        This means that strings need to include quotes in the XML.  Also note
-        that the types are now specified as <a href="http://library.gnome.org/devel/glib/unstable/glib-GVariant.html#GVariant"><span class="type">GVariant</span></a> type strings.
-        </p>
-<pre class="programlisting">
-&lt;type&gt;string&lt;/type&gt;
-&lt;default&gt;rgb&lt;/default&gt;
-        </pre>
-<p>
-        becomes
-        </p>
-<pre class="programlisting">
-&lt;key name="rgba-order" type="s"&gt;
-  &lt;default&gt;'rgb'&lt;/default&gt; &lt;!-- note quotes --&gt;
-&lt;/key&gt;
-        </pre>
-<p>
-      </p>
-<p>
-        Another possible complication is that GConf specifies full paths
-        for each key, while a GSettings schema has a 'path' attribute that
-        contains the prefix for all the keys in the schema, and individual
-        keys just have a simple name. So
-        </p>
-<pre class="programlisting">
-&lt;key&gt;/schemas/desktop/gnome/font_rendering/antialiasing&lt;/key&gt;
-        </pre>
-<p>
-        becomes
-        </p>
-<pre class="programlisting">
-&lt;schema id="org.gnome.font" path="/desktop/gnome/font_rendering/"&gt;
-  &lt;key name="antialiasing" type="s"&gt;
-        </pre>
-<p>
-      </p>
-<p>
-        Default values can be localized in both GConf and GSettings schemas,
-        but GSettings uses gettext for the localization. You can specify
-        the gettext domain to use in the <code class="sgmltag-attribute">gettext-domain</code>
-        attribute. Therefore, when converting localized defaults in GConf,
-        </p>
-<pre class="programlisting">
-&lt;key&gt;/schemas/apps/my_app/font_size&lt;/key&gt;
-  &lt;locale name="C"&gt;
-    &lt;default&gt;18&lt;/default&gt;
-  &lt;/locale&gt;
-  &lt;locale name="be"&gt;
-    &lt;default&gt;24&lt;/default&gt;
-  &lt;/locale&gt;
-&lt;/key&gt;
-        </pre>
-<p>
-        becomes
-        </p>
-<pre class="programlisting">
-&lt;schema id="..." gettext-domain="your-domain"&gt;
- ...
-&lt;key name="font-size" type="i"&gt;
-  &lt;default l10n="messages" context="font_size"&gt;18&lt;/default&gt;
-&lt;/key&gt;
-        </pre>
-<p>
-      </p>
-<p>
-        GSettings uses gettext for translation of default values.
-        The string that is translated is exactly the string that appears
-        inside of the <code class="sgmltag-starttag">&lt;default&gt;</code> element.  This
-        includes the quotation marks that appear around strings.
-        Default values must be marked with the <code class="varname">l10n</code>
-        attribute in the <code class="sgmltag-starttag">&lt;default&gt;</code> tag, which
-        should be set as equal to <code class="literal">'messages'</code> or
-        <code class="literal">'time'</code> depending on the desired category.  An
-        optional translation context can also be specified with the
-        <code class="varname">context</code> attribute, as in the example.  This
-        is usually recommended, since the string "<code class="literal">18</code>"
-        is not particularly easy to translate without context.  The
-        translated version of the default value should be stored in the
-        specified <code class="varname">gettext-domain</code>.  Care must be taken
-        during translation to ensure that all translated values remain
-        syntactically valid; mistakes here will cause runtime errors.
-      </p>
-<p>
-        GSettings schemas have optional <code class="sgmltag-starttag">&lt;summary&gt;</code> and
-        <code class="sgmltag-starttag">&lt;description&gt;</code> elements for each key which
-        correspond to the <code class="sgmltag-starttag">&lt;short&gt;</code> and
-        <code class="sgmltag-starttag">&lt;long&gt;</code> elements in the GConf schema and
-        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. If multiple paragraphs are desired for the description, the
-        paragraphs should be separated by a completely empty line.
-      </p>
-<p>
-        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 <code class="sgmltag-starttag">&lt;_summary&gt;</code>
-        and <code class="sgmltag-starttag">&lt;_description&gt;</code> elements in a
-        .gschema.xml.in file and use
-        <code class="literal">@INTLTOOL_XML_NOMERGE_RULE@</code>
-        in your Makefile.am to produce the .gschema.xml file. The
-        <code class="literal">NOMERGE</code> part of the rule instructs intltool
-        to extract translatable strings, but not merge the translations
-        back into the generated xml file.
-      </p>
-<p>
-        GSettings is a bit more restrictive about key names than GConf. Key
-        names in GSettings can be at most 32 characters long, and must only
-        consist of lowercase characters, numbers and dashes, with no
-        consecutive dashes. The first character must not be a number or dash,
-        and the last character cannot be '-'.
-      </p>
-<p>
-        If you are using the GConf backend for GSettings during the
-        transition, you may want to keep your key names the same they
-        were in GConf, so that existing settings in the users GConf
-        database are preserved. You can achieve this by using the
-        <code class="option">--allow-any-name</code> with the
-        <a href="glib-compile-schemas.html">glib-compile-schemas</a> schema
-        compiler. Note that this option is only meant
-        to ease the process of porting your application, allowing parts
-        of your application to continue to access GConf and parts to use
-        GSettings. By the time you have finished porting your application
-        you must ensure that all key names are valid.
-      </p>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.15.1</div>
-</body>
-</html>