summaryrefslogtreecommitdiff
Side-by-side diff
Diffstat (more/less context) (show whitespace changes)
-rw-r--r--docs/usermanual/i18n.sgm2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm
index d55ebd0..faa0b03 100644
--- a/docs/usermanual/i18n.sgm
+++ b/docs/usermanual/i18n.sgm
@@ -128,25 +128,25 @@
<para>
As a translator one needs to know three different filetypes.
<filename class='extension'>ts</filename>
.ts-files are the most important files for translators. In these files are all strings which
need to be translated and the translations themselfs. All .ts-files are located in
<filename class='directory'>OPIEDIR/i18n/xx</filename> while xx is a languagecode (eg. de or de).
In theory .ts-files are the only ones a translator needs to know.
<filename class='extension'>pro</filename>
Every application has a .pro-file from which the Makefiles are generated. As a translator
you need to check if in every .pro-file is a line for the language you want to translate to.
- This line should look like::
+ This line should look like:
<programlisting>
../../../i18n/de/today.ts \
</programlisting>
Usually the translationcoordinator takes care of these entries so you should not
need to edit them.
<filename class='extension'>qm</filename>
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;.