this should work

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm
index da4a2a8..6ec151f 100644
--- a/docs/usermanual/i18n.sgm
+++ b/docs/usermanual/i18n.sgm
@@ -1,97 +1,97 @@
-<chapter id=i18n>
+<chapter>
 <title>Translations</title>
 <section>
 
 	<para>
 		The &opie;-Project tries to offer the support for as many languages
 		as possible.  In this chapter the process of translating &opie; and its
 		documentation is explained.
 	</para>
 	<para>
 		To ensure that &opie; can be used by as many people as possible the
 		&opie;-project aims to be translated in as many languages as possible. Of
 		course, as there are so many different languages, there is always a lot
 		work to do. Furthermore, &opie; evolves and thus most likely there are
 		translations for applications which should be updated. In this tutorial
 		you will learn how to help &opie; to be available in as many languages as
 		possible and see how easy it is to give something very much respected to
 		the open-source community.
 	</para>
 </section> 
 
 <section>
 	<title>Preferences</title> 
 	
 	<para>
 		In order to translate for &opie; you need an editor to edit the
 		translationfile and preferably access to cvs.  The preferred editor
 		is Linguist. That is an application which comes with &qt;.  It has a
 		intuitive GUI and is very easy to use.  A tutorial can be found <ulink
 		url="http://doc.trolltech.com/3.1/linguist-manual-3.html">here</ulink>.
 	</para> 
 	<para>
 		However, you can use every editor which works with UTF8, for example VIM or
 		EMACS.  The advantage of Linguist is that its GUI is optimized for &opie;s
 		translationfiles and can help you by proposing a translation and notice
 		you if there is an error within the translation.
 	</para> 
 	<para>
 		CVS is a tool which the developers and most translators use to get the source
 		of &opie;.  If you already have an anonymous account for the &opie;-cvs you
 		should go to <filename class='directory'>OPIEDIR/i18n</filename> and do 
 		<programlisting>cvs up</programlisting>.  If there is already a translation for the language you would like to
 		translate you will see the language code in that directory.  For example,
 		for german this is <programlisting>de</programlisting> and for danish it is
 		<programlisting>da</programlisting>.  If not, you should contact the coordinator
 		<personname><firstname>Carsten</firstname><surname>Niehaus</surname></personname>
 		so that everything will be set up for your language.
 	</para>
 </section> 
 
 <section>
 	<title>Styleguide</title> 
 	<para>
 		To ensure a high quality of the translations the translatiors have to keep certain things
 		in mind.
 	</para>
 	<itemizedlist mark='opencircle'>
 		<listitem>
 		<para>
 			The applications do not speak to the user. This means that for example it should not
 			be <errortext>I didn't find the file!</errortext> but <errortext>File not found!</errortext>.
 		</para>
 		</listitem>
 		<listitem>
 		<para>
 			Try not to use exclamationmarks. If the users sees them to often the ! looses it function
 			as a amplifier of a warning.
 		</para>
 		</listitem>
 		<listitem>
 		<para>
 			Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" insteadt
 			of "this is a demonstation !".
 		</para>
 		</listitem>
 	</itemizedlist>
 </section>
 
 <section>
 	<title>Examplecode</title> 
 	
 	<para>
 		In the next paragraph you see an example of how the XML looks like.
 	</para>
 <!--
 	<programlisting>
 		<message> 
 			<source>New</source> 
 			<translation>Neu</translation>
 		</message> 
 		<message> 
 			<source>Today</source>
 			<translation>Heute</translation>
 		</message>
 		<message> 
 			<source>Day</source> 
 			<translation type="unfinished"></translation>