summaryrefslogtreecommitdiff
Side-by-side diff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--docs/usermanual/i18n.sgm5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm
index 6ec151f..3c81d6c 100644
--- a/docs/usermanual/i18n.sgm
+++ b/docs/usermanual/i18n.sgm
@@ -1,28 +1,25 @@
<chapter>
<title>Translations</title>
-<section>
-
<para>
The &opie;-Project tries to offer the support for as many languages
as possible. In this chapter the process of translating &opie; and its
documentation is explained.
</para>
<para>
To ensure that &opie; can be used by as many people as possible the
&opie;-project aims to be translated in as many languages as possible. Of
course, as there are so many different languages, there is always a lot
work to do. Furthermore, &opie; evolves and thus most likely there are
translations for applications which should be updated. In this tutorial
you will learn how to help &opie; to be available in as many languages as
possible and see how easy it is to give something very much respected to
the open-source community.
</para>
-</section>
<section>
<title>Preferences</title>
<para>
In order to translate for &opie; you need an editor to edit the
translationfile and preferably access to cvs. The preferred editor
is Linguist. That is an application which comes with &qt;. It has a
@@ -145,16 +142,17 @@
These are binary files used by &opie; to display the translated strings. They are
automatically generated by calling the command <command>make lrelease</command>. Of course,
you need to have the binary of <application>lrelease</application> which comes with &qt;.
</para>
</section>
<section>
<title>Do's and don'ts</title>
+ <para>
There are certain things that should only be done be the
translationcoordinator or one of the core developers.
<itemizedlist mark='opencircle'>
<listitem>
<para>
The translationfiles should never be updated by the translators. Only the
translationcoordinator updates the repository. This is to avoid merging conflicts.
</para>
@@ -181,11 +179,12 @@
<listitem>
<para>
If you check you translation and see a not translated string even though you translationfile
is 100% translated use the bugtrackingsystem and/or contact the author of that application
directly so that this bug is fixed.
</para>
</listitem>
</itemizedlist>
+ </para>
</section>
</chapter>