1.1 --- a/docs/internationalisation.html Fri Nov 21 01:43:03 2008 +0100
1.2 +++ b/docs/internationalisation.html Fri Nov 21 01:43:30 2008 +0100
1.3 @@ -10,7 +10,7 @@
1.4 document: the usage of different texts, labels or phrases chosen
1.5 according to the languages understood by users of an application. The
1.6 XSLForms toolkit provides two mechanisms for the use of translations
1.7 -and translated phrases:</p><ul><li>The <a href="reference.html#i18n"><code>template:i18n</code></a> attribute, as described in the <a href="reference.html">"Template Attribute Reference"</a> document.</li><li>The <a href="../apidocs/public/XSLForms.Output-module.html#i18n"><code>template:i18n</code></a> extension function, as described in the <a href="../apidocs/public/XSLForms.Output-module.html">extension function API documentation</a>.</li></ul><span style="font-family: sans-serif;"><span style="font-weight: bold;"></span></span><p>Each
1.8 +and translated phrases:</p><ul><li>The <a href="reference.html#i18n"><code>template:i18n</code></a> attribute, as described in the <a href="reference.html">"Template Attribute Reference"</a> document.</li><li>The <a href="../apidocs/XSLForms.Output-module.html#i18n"><code>template:i18n</code></a> extension function, as described in the <a href="../apidocs/XSLForms.Output-module.html">extension function API documentation</a>.</li></ul><span style="font-family: sans-serif;"><span style="font-weight: bold;"></span></span><p>Each
1.9 of the above mechanisms has its own specific purpose in template
1.10 documents, and these purposes are described below, along with the
1.11 necessary procedures for initialising and invoking the translation
1.12 @@ -34,7 +34,7 @@
1.13 attributes, the expression must reside between <code>{</code> and <code>}</code> characters for the evaluation to take place. The anticipated result might resemble something like the following:</p><pre><input type="submit" name="update" value="Oppdatér"/></pre><p>Where
1.14 no suitable translation can be found for the text passed to the
1.15 function, the submitted text is returned as a result, producing
1.16 -something resembling the original, non-translated document fragment.</p><p>See the <a href="../apidocs/public/XSLForms.Output-module.html#i18n"><code>template:i18n</code></a> extension function description in the <a href="../apidocs/public/XSLForms.Output-module.html">extension function API documentation</a> for more details.</p><h2>Initialising and Invoking Translations</h2><p>To
1.17 +something resembling the original, non-translated document fragment.</p><p>See the <a href="../apidocs/XSLForms.Output-module.html#i18n"><code>template:i18n</code></a> extension function description in the <a href="../apidocs/XSLForms.Output-module.html">extension function API documentation</a> for more details.</p><h2>Initialising and Invoking Translations</h2><p>To
1.18 permit the translation of text to occur, we must first prepare the
1.19 translations themselves; then, we must change our application to make
1.20 use of the translations.</p><h3><a name="PreparingTheTranslations"></a>Preparing the Translations</h3><p>Translations