b) Find the language code for the language you are going to translate
into. A list of language codes can be found at
- <URL:http://www.dsv.su.se/~jpalme/ietf/language-codes.html>. If
+ <URL:http://lcweb.loc.gov/standards/iso639-2/langhome.html>. If
there is a 2 letter code for the language, use this.
Create a directory squirrelmail/locale/language_code/LC_MESSAGES/.
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
the directory where the translated squirrelmail.po is residing.
d) Add the language name and language code to the array at the top of
- squirrelmail/functions/i18n.php. For a reference of correct two character
- country codes refer to this <URL:http://palimpsest.stnford.edu/lex/iso639.html>.
+ 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