X-Git-Url: https://vcs.fsf.org/?a=blobdiff_plain;f=doc%2Ftranslating.txt;h=b74bace35accd3551d46515775f9e7fb62d4cf12;hb=b37e457fda0baaf0253ba69f0e5cbdd4845ce242;hp=9320b6c1efebb1a7e5b36617168f0e3d80d3f5cf;hpb=2ce192833aa4f161b1558c2a927d03bedff4afb8;p=squirrelmail.git

diff --git a/doc/translating.txt b/doc/translating.txt
index 9320b6c1..b74bace3 100644
--- a/doc/translating.txt
+++ b/doc/translating.txt
@@ -1,7 +1,7 @@
 How to translate SquirrelMail into another language?
 ====================================================
 
-This document does not deal with CVS and how to upload translations to
+This document does not deal with Subversion and how to upload translations to
 the repository.
 
 1. First time translation
@@ -29,8 +29,18 @@ c) To translate the actual strings fill in the msgstr after each
    running the command "msgfmt -o squirrelmail.mo squirrelmail.po" in
    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.
+d) Create locale/language_code/setup.php file with your translation description.
+   For example locale/tlh/setup.php
+   <?php
+   /* Klingon translation setup */
+   $languages['tlh']['NAME'] = 'Klingon';
+   $languages['tlh']['CHARSET'] = 'utf-8';
+   ?>
+   
+   Before SquirrelMail 1.5.1 translation description should be added to
+   functions/i18n.php. Sample uses only required settings. Translation 
+   description can use other advanced settings. Check include/i18n.php 
+   or SquirrelMail developer's manual.
 
 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