-rw-r--r-- | docs/usermanual/i18n.sgm | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm index 3c81d6c..d2a1f37 100644 --- a/docs/usermanual/i18n.sgm +++ b/docs/usermanual/i18n.sgm | |||
@@ -24,17 +24,17 @@ | |||
24 | translationfile and preferably access to cvs. The preferred editor | 24 | translationfile and preferably access to cvs. The preferred editor |
25 | is Linguist. That is an application which comes with &qt;. It has a | 25 | is Linguist. That is an application which comes with &qt;. It has a |
26 | intuitive GUI and is very easy to use. A tutorial can be found <ulink | 26 | intuitive GUI and is very easy to use. A tutorial can be found <ulink |
27 | url="http://doc.trolltech.com/3.1/linguist-manual-3.html">here</ulink>. | 27 | url="http://doc.trolltech.com/3.1/linguist-manual-3.html">here</ulink>. |
28 | </para> | 28 | </para> |
29 | <para> | 29 | <para> |
30 | However, you can use every editor which works with UTF8, for example VIM or | 30 | However, you can use every editor which works with UTF8, for example VIM or |
31 | EMACS. The advantage of Linguist is that its GUI is optimized for &opie;s | 31 | EMACS. The advantage of Linguist is that its GUI is optimized for &opie;s |
32 | translationfiles and can help you by proposing a translation and notice | 32 | translationfiles and can help you by proposing a translation and warn |
33 | you if there is an error within the translation. | 33 | you if there is an error within the translation. |
34 | </para> | 34 | </para> |
35 | <para> | 35 | <para> |
36 | CVS is a tool which the developers and most translators use to get the source | 36 | CVS is a tool which the developers and most translators use to get the source |
37 | of &opie;. If you already have an anonymous account for the &opie;-cvs you | 37 | of &opie;. If you already have an anonymous account for the &opie;-cvs you |
38 | should go to <filename class='directory'>OPIEDIR/i18n</filename> and do | 38 | should go to <filename class='directory'>OPIEDIR/i18n</filename> and do |
39 | <programlisting>cvs up</programlisting>. If there is already a translation for the language you would like to | 39 | <programlisting>cvs up</programlisting>. If there is already a translation for the language you would like to |
40 | translate you will see the language code in that directory. For example, | 40 | translate you will see the language code in that directory. For example, |
@@ -61,28 +61,28 @@ | |||
61 | <listitem> | 61 | <listitem> |
62 | <para> | 62 | <para> |
63 | Try not to use exclamationmarks. If the users sees them to often the ! looses it function | 63 | Try not to use exclamationmarks. If the users sees them to often the ! looses it function |
64 | as a amplifier of a warning. | 64 | as a amplifier of a warning. |
65 | </para> | 65 | </para> |
66 | </listitem> | 66 | </listitem> |
67 | <listitem> | 67 | <listitem> |
68 | <para> | 68 | <para> |
69 | Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" insteadt | 69 | Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" instead |
70 | of "this is a demonstation !". | 70 | of "this is a demonstation !". |
71 | </para> | 71 | </para> |
72 | </listitem> | 72 | </listitem> |
73 | </itemizedlist> | 73 | </itemizedlist> |
74 | </section> | 74 | </section> |
75 | 75 | ||
76 | <section> | 76 | <section> |
77 | <title>Examplecode</title> | 77 | <title>Examplecode</title> |
78 | 78 | ||
79 | <para> | 79 | <para> |
80 | In the next paragraph you see an example of how the XML looks like. | 80 | In the next paragraph you see an example of what the XML looks like. |
81 | </para> | 81 | </para> |
82 | <!-- | 82 | <!-- |
83 | <programlisting> | 83 | <programlisting> |
84 | <message> | 84 | <message> |
85 | <source>New</source> | 85 | <source>New</source> |
86 | <translation>Neu</translation> | 86 | <translation>Neu</translation> |
87 | </message> | 87 | </message> |
88 | <message> | 88 | <message> |
@@ -113,28 +113,28 @@ | |||
113 | application. The translationcoordinator removes those strings from time to time. In | 113 | application. The translationcoordinator removes those strings from time to time. In |
114 | Linguist those strings are grey and not translatable. | 114 | Linguist those strings are grey and not translatable. |
115 | </para> | 115 | </para> |
116 | </section> | 116 | </section> |
117 | 117 | ||
118 | <section> | 118 | <section> |
119 | <title>Filetypes</title> | 119 | <title>Filetypes</title> |
120 | <para> | 120 | <para> |
121 | As a translator one need to know three different filetypes. | 121 | As a translator one needs to know three different filetypes. |
122 | 122 | ||
123 | <filename class='extension'>ts</filename> | 123 | <filename class='extension'>ts</filename> |
124 | .ts-files are the most important files for translators. In these files are all strings which | 124 | .ts-files are the most important files for translators. In these files are all strings which |
125 | need to be translated and the translations themselfs. All .ts-files are located in | 125 | need to be translated and the translations themselfs. All .ts-files are located in |
126 | <filename class='directory'>OPIEDIR/i18n/xx</filename> while xx is a languagecode (eg. de or de). | 126 | <filename class='directory'>OPIEDIR/i18n/xx</filename> while xx is a languagecode (eg. de or de). |
127 | In theory .ts-files are the only ones a translator needs to know. | 127 | In theory .ts-files are the only ones a translator needs to know. |
128 | 128 | ||
129 | <filename class='extension'>pro</filename> | 129 | <filename class='extension'>pro</filename> |
130 | Every application has a .pro-file from which the Makefiles are generated. As a translator | 130 | Every application has a .pro-file from which the Makefiles are generated. As a translator |
131 | you need to check if in every .pro-file is a line for the language you would to | 131 | you need to check if in every .pro-file is a line for the language you want to translate to. |
132 | translate for. A line like this should look this way: | 132 | This line should look like:: |
133 | 133 | ||
134 | <programlisting> | 134 | <programlisting> |
135 | ../../../i18n/de/today.ts \ | 135 | ../../../i18n/de/today.ts \ |
136 | </programlisting> | 136 | </programlisting> |
137 | 137 | ||
138 | Usually the translationcoordinator takes care of these entries so you should not | 138 | Usually the translationcoordinator takes care of these entries so you should not |
139 | need to edit them. | 139 | need to edit them. |
140 | 140 | ||
@@ -155,36 +155,36 @@ | |||
155 | <para> | 155 | <para> |
156 | The translationfiles should never be updated by the translators. Only the | 156 | The translationfiles should never be updated by the translators. Only the |
157 | translationcoordinator updates the repository. This is to avoid merging conflicts. | 157 | translationcoordinator updates the repository. This is to avoid merging conflicts. |
158 | </para> | 158 | </para> |
159 | </listitem> | 159 | </listitem> |
160 | <listitem> | 160 | <listitem> |
161 | <para> | 161 | <para> |
162 | The binary .qm-files are created by either the translationcoordinator or by the feed-manager. | 162 | The binary .qm-files are created by either the translationcoordinator or by the feed-manager. |
163 | Of course, the translators can created them as described above for testingpurposes but | 163 | Of course, the translators can create them as described above for testing purposes but |
164 | the official files will be provided. | 164 | the official files will be provided. |
165 | </para> | 165 | </para> |
166 | </listitem> | 166 | </listitem> |
167 | <listitem> | 167 | <listitem> |
168 | <para> | 168 | <para> |
169 | Whenever you find a typo or an incorrect message contact the author of the application | 169 | Whenever you find a typo or an incorrect message, contact the author of the application |
170 | and/or use our bugtrackingsystem (Mantis) to make sure this string will be fixed. | 170 | and/or use our bug tracking system (Mantis) to make sure this string will be fixed. |
171 | </para> | 171 | </para> |
172 | </listitem> | 172 | </listitem> |
173 | <listitem> | 173 | <listitem> |
174 | <para> | 174 | <para> |
175 | If you find a string like "Form1" contact the translationcoordinator. These strings | 175 | If you find a string like "Form1" contact the translation coordinator. These strings |
176 | should not be in the translationfiles. You don't need to translate them. | 176 | should not be in the translationfiles. You don't need to translate them. |
177 | </para> | 177 | </para> |
178 | </listitem> | 178 | </listitem> |
179 | <listitem> | 179 | <listitem> |
180 | <para> | 180 | <para> |
181 | If you check you translation and see a not translated string even though you translationfile | 181 | If you check you translation and see an un-translated string even though your translationfile |
182 | is 100% translated use the bugtrackingsystem and/or contact the author of that application | 182 | is 100% translated use the bug tracking system and/or contact the author of that application |
183 | directly so that this bug is fixed. | 183 | directly so that this bug is fixed. |
184 | </para> | 184 | </para> |
185 | </listitem> | 185 | </listitem> |
186 | </itemizedlist> | 186 | </itemizedlist> |
187 | </para> | 187 | </para> |
188 | </section> | 188 | </section> |
189 | 189 | ||
190 | </chapter> | 190 | </chapter> |