:%s/::$/:/

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 @@
                 not.  This is marked by the 
                 
                 <programlisting>type="unfinished"</programlisting>
                 
         </para> 
         <para>
                 If you choose to use an editor like VIM instead of the prefered tool
                 -Linguist- you have to remove that mark and add the translated string
                 between the two translation-tags.
         </para>
         <para>
                 It might happen that you see <emphasis>type="obsolete"</emphasis> in a
                 .ts-file. You should not translate these stings as they do no longer appear in the
                 application. The translationcoordinator removes those strings from time to time. In
                 Linguist those strings are grey and not translatable.
         </para>
 </section> 
 
 <section>
         <title>Filetypes</title>
         <para>
                 As a translator one needs to know three different filetypes.
                 
                 <filename class='extension'>ts</filename>
                 .ts-files are the most important files for translators.  In these files are all strings which
                 need to be translated and the translations themselfs.  All .ts-files are located in 
                 <filename class='directory'>OPIEDIR/i18n/xx</filename> while xx is a languagecode (eg. de or de).  
                 In theory .ts-files are the only ones a translator needs to know.
                 
                 <filename class='extension'>pro</filename>
                 Every application has a .pro-file from which the Makefiles are generated.  As a translator
                 you need to check if in every .pro-file is a line for the language you want to translate to.  
-                This line should look like::
+                This line should look like:
 
                 <programlisting>
                          ../../../i18n/de/today.ts \
                 </programlisting>
                 
                 Usually the translationcoordinator takes care of these entries so you should not
                 need to edit them.
                 
                 <filename class='extension'>qm</filename>
                 These are binary files used by &opie; to display the translated strings.  They are
                 automatically generated by calling the command <command>make lrelease</command>.  Of course,
                 you need to have the binary of <application>lrelease</application> which comes with &qt;.
         </para>
 </section>
 
 <section>
         <title>Do's and don'ts</title> 
         <para>
         There are certain things that should only be done be the
         translationcoordinator or one of the core developers.
         <itemizedlist mark='opencircle'>
                 <listitem>
                 <para>
                         The translationfiles should never be updated by the translators.  Only the 
                         translationcoordinator updates the repository.  This is to avoid merging conflicts.  
                 </para>
                 </listitem>
                 <listitem>
                 <para>
                         The binary .qm-files are created by either the translationcoordinator or by the feed-manager.
                         Of course, the translators can create them as described above for testing purposes but 
                         the official files will be provided.