Misc. documentation fixes by Simon Dick.

[squirrelmail.git] / doc / translating.txt

diff --git a/doc/translating.txt b/doc/translating.txt
index cdb4debbe30826c978cd2b1fb8aa0c6ba612d18e..5f26e1ade2dc91a1de8cf192e8eff79b7daa890e 100644 (file)
--- a/doc/translating.txt
+++ b/doc/translating.txt
@@ -20,9 +20,9 @@ b) Find the language code for the language you are going to translate
    Copy squirrelmail/po/squirrelmail.po into this directory. This is the
    file that is going to be translated.
 
-c) To translate the actual strings fill inn the msgstr after each
+c) To translate the actual strings fill in the msgstr after each
    msgid with the appropiate translation. There are a few tools which
-   kan make this job a bit easier at
+   can make this job a bit easier at
    <URL:http://i18n.kde.org/translation-howto/gui-specialized-apps.html>.
 
    Convert the translated squirrelmail.po into a binary file by
@@ -32,13 +32,16 @@ c) To translate the actual strings fill inn the msgstr after each
 d) Add the language name and language code to the array at the top of
    squirrelmail/functions/i18n.php.
 
+There is also a small script in the po/ directory that can help in
+creating charset mappings from the mappings files that are provided by
+the Unicode consortium.
 
 2. Maintaining translations
 ---------------------------
 
-the text strings in the program will change over time. This means that
-strings that are already translated is no longer used and new strings
-are added. Therefore it is neccessary to maintain the translations.
+The text strings in the program will change over time. This means that
+strings that are already translated are no longer used and new strings
+are added. Therefore it is necessary to maintain the translations.
 
 a) There should always be an updated template containing all strings
    in SquirrelMail in squirrelmail/squirrelmail.po. To merge all new