| -rw-r--r-- | docs/usermanual/i18n.sgm | 5 |
1 files changed, 2 insertions, 3 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 @@ </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> </message> </programlisting> - - </para> +--> <para> As you can see the markup is very simple. The part between two source-tags is the english text which appears if there is no translation yet. In the first case this is <quote>New</quote>. The next row is where the translated string would be. The first two messages are already translated, the third is 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 <programlisting>translation</programlisting>-tags. </para> <para> It might happen that you see <programlisting>type="obsolete"</programlisting> 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 |