-rw-r--r-- | docs/usermanual/i18n.sgm | 2 |
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 | |||
@@ -108,65 +108,65 @@ | |||
108 | not. This is marked by the | 108 | not. This is marked by the |
109 | 109 | ||
110 | <programlisting>type="unfinished"</programlisting> | 110 | <programlisting>type="unfinished"</programlisting> |
111 | 111 | ||
112 | </para> | 112 | </para> |
113 | <para> | 113 | <para> |
114 | If you choose to use an editor like VIM instead of the prefered tool | 114 | If you choose to use an editor like VIM instead of the prefered tool |
115 | -Linguist- you have to remove that mark and add the translated string | 115 | -Linguist- you have to remove that mark and add the translated string |
116 | between the two translation-tags. | 116 | between the two translation-tags. |
117 | </para> | 117 | </para> |
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 stings as they do no longer appear in the |
121 | application. The translationcoordinator removes those strings from time to time. In | 121 | application. The translationcoordinator 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> |
124 | </section> | 124 | </section> |
125 | 125 | ||
126 | <section> | 126 | <section> |
127 | <title>Filetypes</title> | 127 | <title>Filetypes</title> |
128 | <para> | 128 | <para> |
129 | As a translator one needs to know three different filetypes. | 129 | As a translator one needs to know three different filetypes. |
130 | 130 | ||
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 themselfs. 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. |
136 | 136 | ||
137 | <filename class='extension'>pro</filename> | 137 | <filename class='extension'>pro</filename> |
138 | Every application has a .pro-file from which the Makefiles are generated. As a translator | 138 | Every application has a .pro-file from which the Makefiles are generated. As a translator |
139 | you need to check if in every .pro-file is a line for the language you want to translate to. | 139 | you need to check if in every .pro-file is a line for the language you want to translate to. |
140 | This line should look like:: | 140 | This line should look like: |
141 | 141 | ||
142 | <programlisting> | 142 | <programlisting> |
143 | ../../../i18n/de/today.ts \ | 143 | ../../../i18n/de/today.ts \ |
144 | </programlisting> | 144 | </programlisting> |
145 | 145 | ||
146 | Usually the translationcoordinator takes care of these entries so you should not | 146 | Usually the translationcoordinator takes care of these entries so you should not |
147 | need to edit them. | 147 | need to edit them. |
148 | 148 | ||
149 | <filename class='extension'>qm</filename> | 149 | <filename class='extension'>qm</filename> |
150 | These are binary files used by &opie; to display the translated strings. They are | 150 | These are binary files used by &opie; to display the translated strings. They are |
151 | automatically generated by calling the command <command>make lrelease</command>. Of course, | 151 | automatically generated by calling the command <command>make lrelease</command>. Of course, |
152 | you need to have the binary of <application>lrelease</application> which comes with &qt;. | 152 | you need to have the binary of <application>lrelease</application> which comes with &qt;. |
153 | </para> | 153 | </para> |
154 | </section> | 154 | </section> |
155 | 155 | ||
156 | <section> | 156 | <section> |
157 | <title>Do's and don'ts</title> | 157 | <title>Do's and don'ts</title> |
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 | translationcoordinator 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 translationfiles should never be updated by the translators. Only the |
165 | translationcoordinator updates the repository. This is to avoid merging conflicts. | 165 | translationcoordinator 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 translationcoordinator 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. |