| author | spiralman <spiralman> | 2002-12-13 21:40:10 (UTC) |
|---|---|---|
| committer | spiralman <spiralman> | 2002-12-13 21:40:10 (UTC) |
| commit | d00761e2b3b69e1edddcb2115c4c0ae6b5aa4265 (patch) (side-by-side diff) | |
| tree | 2fe917d1fbd34995a88ff7acafc788933bb697e3 | |
| parent | d09bfeb9e60ec5bc86e0143029c08e431c733f60 (diff) | |
| download | opie-d00761e2b3b69e1edddcb2115c4c0ae6b5aa4265.zip opie-d00761e2b3b69e1edddcb2115c4c0ae6b5aa4265.tar.gz opie-d00761e2b3b69e1edddcb2115c4c0ae6b5aa4265.tar.bz2 | |
fixed minor typos and gramatical errors
| -rw-r--r-- | docs/usermanual/i18n.sgm | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm index 3c81d6c..d2a1f37 100644 --- a/docs/usermanual/i18n.sgm +++ b/docs/usermanual/i18n.sgm @@ -31,3 +31,3 @@ 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 + translationfiles and can help you by proposing a translation and warn you if there is an error within the translation. @@ -68,3 +68,3 @@ <para> - Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" insteadt + Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" instead of "this is a demonstation !". @@ -79,3 +79,3 @@ <para> - In the next paragraph you see an example of how the XML looks like. + In the next paragraph you see an example of what the XML looks like. </para> @@ -120,3 +120,3 @@ <para> - As a translator one need to know three different filetypes. + As a translator one needs to know three different filetypes. @@ -130,4 +130,4 @@ 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 would to - translate for. A line like this should look this way: + 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:: @@ -162,3 +162,3 @@ The binary .qm-files are created by either the translationcoordinator or by the feed-manager. - Of course, the translators can created them as described above for testingpurposes but + Of course, the translators can create them as described above for testing purposes but the official files will be provided. @@ -168,4 +168,4 @@ <para> - Whenever you find a typo or an incorrect message contact the author of the application - and/or use our bugtrackingsystem (Mantis) to make sure this string will be fixed. + Whenever you find a typo or an incorrect message, contact the author of the application + and/or use our bug tracking system (Mantis) to make sure this string will be fixed. </para> @@ -174,3 +174,3 @@ <para> - If you find a string like "Form1" contact the translationcoordinator. These strings + 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. @@ -180,4 +180,4 @@ <para> - If you check you translation and see a not translated string even though you translationfile - is 100% translated use the bugtrackingsystem and/or contact the author of that application + If you check you translation and see an un-translated string even though your translationfile + is 100% translated use the bug tracking system and/or contact the author of that application directly so that this bug is fixed. |