From de0161ecfae40c677f3c03a8c0efe6a089e422b8 Mon Sep 17 00:00:00 2001 From: sandman Date: Mon, 23 Dec 2002 14:11:12 +0000 Subject: applied a patch for carsten niehaus (fixes some typos) --- (limited to 'docs') diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm index faa0b03..0c52392 100644 --- a/docs/usermanual/i18n.sgm +++ b/docs/usermanual/i18n.sgm @@ -8,7 +8,7 @@ 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 + course, as there are so many different languages, there is always a lot of 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 @@ -21,7 +21,7 @@ In order to translate for &opie; you need an editor to edit the - translationfile and preferably access to cvs. The preferred editor + translation file 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 here. @@ -29,7 +29,7 @@ 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 warn + translation files and can help you by proposing a translation and warn you if there is an error within the translation. @@ -54,7 +54,7 @@
Styleguide - To ensure a high quality of the translations the translatiors have to keep certain things + To ensure a high quality of the translations the translators have to keep certain things in mind. @@ -66,14 +66,14 @@ - Try not to use exclamationmarks. If the users sees them to often the ! looses it function - as a amplifier of a warning. + Try not to use exclamation marks. If the users see them to often the ! looses it function + as an amplifier of a warning. - Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" instead - of "this is a demonstation !". + Don't put a space in front of a punctuation mark. So write eg "this is a demonstration!" instead + of "this is a demonstration !". @@ -117,8 +117,8 @@ It might happen that you see type="obsolete" 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 + .ts-file. You should not translate these strings as they do no longer appear in the + application. The translation coordinator removes those strings from time to time. In Linguist those strings are grey and not translatable.
@@ -130,7 +130,7 @@ ts .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 + need to be translated and the translations themselves. All .ts-files are located in OPIEDIR/i18n/xx while xx is a languagecode (eg. de or de). In theory .ts-files are the only ones a translator needs to know. @@ -143,7 +143,7 @@ ../../../i18n/de/today.ts \ - Usually the translationcoordinator takes care of these entries so you should not + Usually the translation coordinator takes care of these entries so you should not need to edit them. qm @@ -157,17 +157,17 @@ Do's and don'ts There are certain things that should only be done be the - translationcoordinator or one of the core developers. + translation coordinator or one of the core developers. - The translationfiles should never be updated by the translators. Only the - translationcoordinator updates the repository. This is to avoid merging conflicts. + The translation files should never be updated by the translators. Only the + translation coordinator updates the repository. This is to avoid merging conflicts. - The binary .qm-files are created by either the translationcoordinator or by the feed-manager. + The binary .qm-files are created by either the translation coordinator 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. @@ -181,12 +181,12 @@ If you find a string like "Form1" contact the translation coordinator. These strings - should not be in the translationfiles. You don't need to translate them. + should not be in the translation files. You don't need to translate them. - If you check you translation and see an un-translated string even though your translationfile + If you check your translation and see an un-translated string even though your translation file is 100% translated use the bug tracking system and/or contact the author of that application directly so that this bug is fixed. -- cgit v0.9.0.2