summaryrefslogtreecommitdiff
authorcniehaus <cniehaus>2002-12-13 14:36:19 (UTC)
committer cniehaus <cniehaus>2002-12-13 14:36:19 (UTC)
commita92357d9bfc231eafdb7798ed4b098c796ff5ec8 (patch) (unidiff)
tree01b5a752d87b72710df363f50acdc2d927ecaf32
parent5ea897449291a10155880a49095c642dc508442c (diff)
downloadopie-a92357d9bfc231eafdb7798ed4b098c796ff5ec8.zip
opie-a92357d9bfc231eafdb7798ed4b098c796ff5ec8.tar.gz
opie-a92357d9bfc231eafdb7798ed4b098c796ff5ec8.tar.bz2
oops
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--docs/usermanual/i18n.sgm7
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
@@ -69,49 +69,48 @@
69 </listitem> 69 </listitem>
70 <listitem> 70 <listitem>
71 <para> 71 <para>
72 Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" insteadt 72 Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" insteadt
73 of "this is a demonstation !". 73 of "this is a demonstation !".
74 </para> 74 </para>
75 </listitem> 75 </listitem>
76 </itemizedlist> 76 </itemizedlist>
77</section> 77</section>
78 78
79<section> 79<section>
80 <title>Examplecode</title> 80 <title>Examplecode</title>
81 81
82 <para> 82 <para>
83 In the next paragraph you see an example of how the XML looks like. 83 In the next paragraph you see an example of how the XML looks like.
84 </para> 84 </para>
85 85<!--
86 <programlisting> 86 <programlisting>
87 <message> 87 <message>
88 <source>New</source> 88 <source>New</source>
89 <translation>Neu</translation> 89 <translation>Neu</translation>
90 </message> 90 </message>
91 <message> 91 <message>
92 <source>Today</source> 92 <source>Today</source>
93 <translation>Heute</translation> 93 <translation>Heute</translation>
94 </message> 94 </message>
95 <message> 95 <message>
96 <source>Day</source> 96 <source>Day</source>
97 <translation type="unfinished"></translation> 97 <translation type="unfinished"></translation>
98 </message> 98 </message>
99 </programlisting> 99 </programlisting>
100 100-->
101 </para>
102 <para> 101 <para>
103 As you can see the markup is very simple. The part between two source-tags is 102 As you can see the markup is very simple. The part between two source-tags is
104 the english text which appears if there is no translation yet. In the first 103 the english text which appears if there is no translation yet. In the first
105 case this is <quote>New</quote>. The next row is where the translated string 104 case this is <quote>New</quote>. The next row is where the translated string
106 would be. The first two messages are already translated, the third is 105 would be. The first two messages are already translated, the third is
107 not. This is marked by the <programlisting>type="unfinished"</programlisting>. 106 not. This is marked by the <programlisting>type="unfinished"</programlisting>.
108 </para> 107 </para>
109 <para> 108 <para>
110 If you choose to use an editor like VIM instead of the prefered tool 109 If you choose to use an editor like VIM instead of the prefered tool
111 -Linguist- you have to remove that mark and add the translated string 110 -Linguist- you have to remove that mark and add the translated string
112 between the two <programlisting>translation</programlisting>-tags. 111 between the two <programlisting>translation</programlisting>-tags.
113 </para> 112 </para>
114 <para> 113 <para>
115 It might happen that you see <programlisting>type="obsolete"</programlisting> in a 114 It might happen that you see <programlisting>type="obsolete"</programlisting> in a
116 .ts-file. You should not translate these stings as they do no longer appear in the 115 .ts-file. You should not translate these stings as they do no longer appear in the
117 application. The translationcoordinator removes those strings from time to time. In 116 application. The translationcoordinator removes those strings from time to time. In
@@ -139,33 +138,33 @@
139 ../../../i18n/de/today.ts \ 138 ../../../i18n/de/today.ts \
140 </programlisting> 139 </programlisting>
141 140
142 Usually the translationcoordinator takes care of these entries so you should not 141 Usually the translationcoordinator takes care of these entries so you should not
143 need to edit them. 142 need to edit them.
144 143
145 <filename class='extension'>qm</filename> 144 <filename class='extension'>qm</filename>
146 These are binary files used by &opie; to display the translated strings. They are 145 These are binary files used by &opie; to display the translated strings. They are
147 automatically generated by calling the command <command>make lrelease</command>. Of course, 146 automatically generated by calling the command <command>make lrelease</command>. Of course,
148 you need to have the binary of <application>lrelease</application> which comes with &qt;. 147 you need to have the binary of <application>lrelease</application> which comes with &qt;.
149 </para> 148 </para>
150</section> 149</section>
151 150
152<section> 151<section>
153 <title>Do's and don'ts</title> 152 <title>Do's and don'ts</title>
154 There are certain things that should only be done be the 153 There are certain things that should only be done be the
155 translationcoordinator or one of the core developers. 154 translationcoordinator or one of the core developers.
156 <itemizedlist mark='opencircle'> 155 <itemizedlist mark='opencircle'>
157 <listitem> 156 <listitem>
158 <para> 157 <para>
159 The translationfiles should never be updated by the translators. Only the 158 The translationfiles should never be updated by the translators. Only the
160 translationcoordinator updates the repository. This is to avoid merging conflicts. 159 translationcoordinator updates the repository. This is to avoid merging conflicts.
161 </para> 160 </para>
162 </listitem> 161 </listitem>
163 <listitem> 162 <listitem>
164 <para> 163 <para>
165 The binary .qm-files are created by either the translationcoordinator or by the feed-manager. 164 The binary .qm-files are created by either the translationcoordinator or by the feed-manager.
166 Of course, the translators can created them as described above for testingpurposes but 165 Of course, the translators can created them as described above for testingpurposes but
167 the official files will be provided. 166 the official files will be provided.
168 </para> 167 </para>
169 </listitem> 168 </listitem>
170 <listitem> 169 <listitem>
171 <para> 170 <para>