author | sandman <sandman> | 2002-12-23 14:11:12 (UTC) |
---|---|---|
committer | sandman <sandman> | 2002-12-23 14:11:12 (UTC) |
commit | de0161ecfae40c677f3c03a8c0efe6a089e422b8 (patch) (unidiff) | |
tree | 22e0c2145fd4724854bedc924b868e682d62c585 /docs/usermanual | |
parent | 8e5f0da214b389213ab9c00e7c5e93e0a9fbac46 (diff) | |
download | opie-de0161ecfae40c677f3c03a8c0efe6a089e422b8.zip opie-de0161ecfae40c677f3c03a8c0efe6a089e422b8.tar.gz opie-de0161ecfae40c677f3c03a8c0efe6a089e422b8.tar.bz2 |
applied a patch for carsten niehaus (fixes some typos)
-rw-r--r-- | docs/usermanual/i18n.sgm | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm index faa0b03..0c52392 100644 --- a/docs/usermanual/i18n.sgm +++ b/docs/usermanual/i18n.sgm | |||
@@ -9,5 +9,5 @@ | |||
9 | To ensure that &opie; can be used by as many people as possible the | 9 | To ensure that &opie; can be used by as many people as possible the |
10 | &opie;-project aims to be translated in as many languages as possible. Of | 10 | &opie;-project aims to be translated in as many languages as possible. Of |
11 | course, as there are so many different languages, there is always a lot | 11 | course, as there are so many different languages, there is always a lot of |
12 | work to do. Furthermore, &opie; evolves and thus most likely there are | 12 | work to do. Furthermore, &opie; evolves and thus most likely there are |
13 | translations for applications which should be updated. In this tutorial | 13 | translations for applications which should be updated. In this tutorial |
@@ -22,5 +22,5 @@ | |||
22 | <para> | 22 | <para> |
23 | In order to translate for &opie; you need an editor to edit the | 23 | In order to translate for &opie; you need an editor to edit the |
24 | translationfile and preferably access to cvs. The preferred editor | 24 | translation file 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 |
@@ -30,5 +30,5 @@ | |||
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 warn | 32 | translation files 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> |
@@ -55,5 +55,5 @@ | |||
55 | <title>Styleguide</title> | 55 | <title>Styleguide</title> |
56 | <para> | 56 | <para> |
57 | To ensure a high quality of the translations the translatiors have to keep certain things | 57 | To ensure a high quality of the translations the translators have to keep certain things |
58 | in mind. | 58 | in mind. |
59 | </para> | 59 | </para> |
@@ -67,12 +67,12 @@ | |||
67 | <listitem> | 67 | <listitem> |
68 | <para> | 68 | <para> |
69 | Try not to use exclamationmarks. If the users sees them to often the ! looses it function | 69 | Try not to use exclamation marks. If the users see them to often the ! looses it function |
70 | as a amplifier of a warning. | 70 | as an amplifier of a warning. |
71 | </para> | 71 | </para> |
72 | </listitem> | 72 | </listitem> |
73 | <listitem> | 73 | <listitem> |
74 | <para> | 74 | <para> |
75 | Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" instead | 75 | Don't put a space in front of a punctuation mark. So write eg "this is a demonstration!" instead |
76 | of "this is a demonstation !". | 76 | of "this is a demonstration !". |
77 | </para> | 77 | </para> |
78 | </listitem> | 78 | </listitem> |
@@ -118,6 +118,6 @@ | |||
118 | <para> | 118 | <para> |
119 | It might happen that you see <emphasis>type="obsolete"</emphasis> in a | 119 | It might happen that you see <emphasis>type="obsolete"</emphasis> in a |
120 | .ts-file. You should not translate these stings as they do no longer appear in the | 120 | .ts-file. You should not translate these strings as they do no longer appear in the |
121 | application. The translationcoordinator removes those strings from time to time. In | 121 | application. The translation coordinator removes those strings from time to time. In |
122 | Linguist those strings are grey and not translatable. | 122 | Linguist those strings are grey and not translatable. |
123 | </para> | 123 | </para> |
@@ -131,5 +131,5 @@ | |||
131 | <filename class='extension'>ts</filename> | 131 | <filename class='extension'>ts</filename> |
132 | .ts-files are the most important files for translators. In these files are all strings which | 132 | .ts-files are the most important files for translators. In these files are all strings which |
133 | need to be translated and the translations themselfs. All .ts-files are located in | 133 | need to be translated and the translations themselves. All .ts-files are located in |
134 | <filename class='directory'>OPIEDIR/i18n/xx</filename> while xx is a languagecode (eg. de or de). | 134 | <filename class='directory'>OPIEDIR/i18n/xx</filename> while xx is a languagecode (eg. de or de). |
135 | In theory .ts-files are the only ones a translator needs to know. | 135 | In theory .ts-files are the only ones a translator needs to know. |
@@ -144,5 +144,5 @@ | |||
144 | </programlisting> | 144 | </programlisting> |
145 | 145 | ||
146 | Usually the translationcoordinator takes care of these entries so you should not | 146 | Usually the translation coordinator takes care of these entries so you should not |
147 | need to edit them. | 147 | need to edit them. |
148 | 148 | ||
@@ -158,15 +158,15 @@ | |||
158 | <para> | 158 | <para> |
159 | There are certain things that should only be done be the | 159 | There are certain things that should only be done be the |
160 | translationcoordinator or one of the core developers. | 160 | translation coordinator or one of the core developers. |
161 | <itemizedlist mark='opencircle'> | 161 | <itemizedlist mark='opencircle'> |
162 | <listitem> | 162 | <listitem> |
163 | <para> | 163 | <para> |
164 | The translationfiles should never be updated by the translators. Only the | 164 | The translation files should never be updated by the translators. Only the |
165 | translationcoordinator updates the repository. This is to avoid merging conflicts. | 165 | translation coordinator updates the repository. This is to avoid merging conflicts. |
166 | </para> | 166 | </para> |
167 | </listitem> | 167 | </listitem> |
168 | <listitem> | 168 | <listitem> |
169 | <para> | 169 | <para> |
170 | The binary .qm-files are created by either the translationcoordinator or by the feed-manager. | 170 | The binary .qm-files are created by either the translation coordinator or by the feed-manager. |
171 | Of course, the translators can create them as described above for testing purposes but | 171 | Of course, the translators can create them as described above for testing purposes but |
172 | the official files will be provided. | 172 | the official files will be provided. |
@@ -182,10 +182,10 @@ | |||
182 | <para> | 182 | <para> |
183 | If you find a string like "Form1" contact the translation coordinator. These strings | 183 | If you find a string like "Form1" contact the translation coordinator. These strings |
184 | should not be in the translationfiles. You don't need to translate them. | 184 | should not be in the translation files. You don't need to translate them. |
185 | </para> | 185 | </para> |
186 | </listitem> | 186 | </listitem> |
187 | <listitem> | 187 | <listitem> |
188 | <para> | 188 | <para> |
189 | If you check you translation and see an un-translated string even though your translationfile | 189 | If you check your translation and see an un-translated string even though your translation file |
190 | is 100% translated use the bug tracking system and/or contact the author of that application | 190 | is 100% translated use the bug tracking system and/or contact the author of that application |
191 | directly so that this bug is fixed. | 191 | directly so that this bug is fixed. |