author | cniehaus <cniehaus> | 2002-12-13 14:36:19 (UTC) |
---|---|---|
committer | cniehaus <cniehaus> | 2002-12-13 14:36:19 (UTC) |
commit | a92357d9bfc231eafdb7798ed4b098c796ff5ec8 (patch) (side-by-side diff) | |
tree | 01b5a752d87b72710df363f50acdc2d927ecaf32 | |
parent | 5ea897449291a10155880a49095c642dc508442c (diff) | |
download | opie-a92357d9bfc231eafdb7798ed4b098c796ff5ec8.zip opie-a92357d9bfc231eafdb7798ed4b098c796ff5ec8.tar.gz opie-a92357d9bfc231eafdb7798ed4b098c796ff5ec8.tar.bz2 |
oops
-rw-r--r-- | docs/usermanual/i18n.sgm | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm index b1ac33a..577e733 100644 --- a/docs/usermanual/i18n.sgm +++ b/docs/usermanual/i18n.sgm @@ -73,41 +73,40 @@ of "this is a demonstation !". </para> </listitem> </itemizedlist> </section> <section> <title>Examplecode</title> <para> In the next paragraph you see an example of how the XML looks like. </para> - +<!-- <programlisting> <message> <source>New</source> <translation>Neu</translation> </message> <message> <source>Today</source> <translation>Heute</translation> </message> <message> <source>Day</source> <translation type="unfinished"></translation> </message> </programlisting> - - </para> +--> <para> As you can see the markup is very simple. The part between two source-tags is the english text which appears if there is no translation yet. In the first case this is <quote>New</quote>. The next row is where the translated string would be. The first two messages are already translated, the third is not. This is marked by the <programlisting>type="unfinished"</programlisting>. </para> <para> If you choose to use an editor like VIM instead of the prefered tool -Linguist- you have to remove that mark and add the translated string between the two <programlisting>translation</programlisting>-tags. </para> @@ -143,25 +142,25 @@ 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;. </para> </section> <section> <title>Do's and don'ts</title> There are certain things that should only be done be the - translationcoordinator or one of the core developers. + 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> </listitem> <listitem> <para> The binary .qm-files are created by either the translationcoordinator or by the feed-manager. Of course, the translators can created them as described above for testingpurposes but the official files will be provided. |