summaryrefslogtreecommitdiff
authorcniehaus <cniehaus>2002-12-07 20:35:26 (UTC)
committer cniehaus <cniehaus>2002-12-07 20:35:26 (UTC)
commit06611e529c9d7b28764f1fe16f241e111247f928 (patch) (unidiff)
tree76b469554bfbaeedd8375593095c581555722637
parent20b6e9b4632308bd12e37ced57d046e7938d39f8 (diff)
downloadopie-06611e529c9d7b28764f1fe16f241e111247f928.zip
opie-06611e529c9d7b28764f1fe16f241e111247f928.tar.gz
opie-06611e529c9d7b28764f1fe16f241e111247f928.tar.bz2
update. Spiralman: _please_ check my syntax!
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--docs/usermanual/i18n.sgm62
1 files changed, 60 insertions, 2 deletions
diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm
index 8b199fc..1964f50 100644
--- a/docs/usermanual/i18n.sgm
+++ b/docs/usermanual/i18n.sgm
@@ -7,5 +7,10 @@
7 <title>Introduction</title> 7 <title>Introduction</title>
8 <para> 8 <para>
9 test blah blah 9 To ensure that OPIE can be used by as many people as possible the OPIE-project
10 aims to be translated in as many languages as possible. Of course, as there are so many
11 different languages, there is always a lot work to do. Furthermore, OPIE evolves and thus
12 most likely there are translations for applications which should be updated. In this tutorial
13 you will learn how to help OPIE to be availeble in as many languages as possible and see how
14 easy it is to give something very much respected to the open-source community.
10 </para> 15 </para>
11</section> 16</section>
@@ -14,5 +19,58 @@
14 <para> 19 <para>
15 In order to translate for OPIE you need an editor to edit the translationfile 20 In order to translate for OPIE you need an editor to edit the translationfile
16 and preferably access to cvs. 21 and preferably access to cvs. The preferred editor is Linguist. That is an application which
22 comes with Qt. It has a intuitive GUI and is very easy to use. A tutorial can be found here:
23 <link>http://doc.trolltech.com/3.1/linguist-manual-3.html</link>.
24 </para>
25 <para>
26 However, you can use every editor which works with UTF8, for example VIM or EMACS. The advantage
27 of Linguist is that its GUI is optimized for OPIEs translationfiles and can help you be
28 proposing a translation and notice you if there is an error within the translation.
29 </para>
30 <para>
31 CVS is a tool which the developers and most translators use to get the source of OPIE. If you
32 already have an anonymous account for the OPIE-cvs you should go to $OPIEDIR/i18n and do <code>cvs up</code>.
33 If there is already a translation for the language you would like to translate you will see
34 the language code in that directory. For example, for german this is <code>de</code> and for danish
35 it is <code>da</code>. If not you should contact the coordinator Carsten Niehaus so that
36 everything will be set up for your language.
37 </para>
38</section>
39<section>
40 <title>Examplecode</title>
41 <para>
42 In the next paragraph you see an example of how the XML looks like.
43 </para>
44 <!--
45 <message>
46 <source>New</source>
47 <translation>Neu</translation>
48 </message>
49 <message>
50 <source>Today</source>
51 <translation>Heute</translation>
52 </message>
53 <message>
54 <source>Day</source>
55 <translation type="unfinished"></translation>
56 </message>
57 -->
58 </para>
59 <para>
60 As you can see the markup is very simple. The part between two source-tags is the english
61 text which appears if there is no translation yet. In the first case this is <quote>New</quote>.
62 In the next rowis where the translation would be. The first two messages are already translated,
63 the third is not. This is marked by the <code>type="unfinished"</code>.
64 </para>
65 <para>
66 If you choose to use an editor like vim instead of the prefered tool -Linguist- you have to remove
67 that mark and add the translated string between the two <code>translation</code>-tags.
68 </para>
69</section>
70<section>
71 <title>Do's and don'ts</title>
72 <para>
73 There are certain things that should only be done be the translationcoordinator or one of the
74 core developers.
17 </para> 75 </para>
18</section> 76</section>