Updated some instructions on how to get i18n working. Most notably,

the addlang script is being removed since lists can now enable any
site-available language thru-the-web.

"ha" => "xx"

Also update the list of supported languages and a list of promised
languages.

1 files changed, 28 insertions, 37 deletions

diff --git a/README-I18N.en b/README-I18N.en
index 1c3a4ed36..6df4d6c6d 100644
--- a/README-I18N.en
+++ b/README-I18N.en
@@ -8,36 +8,9 @@ INTERNATIONALIZATION
     Mailman 2.1 is multilingual.  By default it supports English, but
     additional languages may also be available.  If the language you
     want to add is already supported by Mailman, then getting all your
-    lists to also support that language is fairly easy.  You first
-    need to run the "addlang" script at the command line, giving it
-    the names of the list to add language support to.
-
-    Let's say for example, you're adding Spanish support.  You should
-    do the following:
-
-        % cd $prefix (the Mailman installation directory)
-        % bin/addlang -l mylist es
-
-    This will add Spanish support to mylist, provided that following
-    is true (all relative to the $prefix directory):
-
-    1. There must be a file messages/es/LC_MESSAGES/mailman.mo file
-       which contains the catalog of translations for translatable
-       strings in the Mailman source code.
-
-    2. There must be a directory templates/es which contains all the
-       global default translated template files for Spanish.
-
-    3. There is an entry in the Mailman/Defaults.py file for the 'es'
-       language in the constant LC_DESCRIPTIONS.  If not, do not
-       change Defaults.py!  Instead add the following in your
-       mm_cfg.py file (again, the example here is for Spanish):
-
-       add_language('es', 'Spanish (Spain)', 'iso-8859-1')
-
-       The add_language() function takes three arguments (as strings):
-       the language code, the language description, and the language
-       charset.
+    lists to also support that language is fairly easy.  You just need
+    to go to the administrative web pages, click on the "Languages"
+    category, and select the languages you want your list to support.
 
     If the language you want to use has not been previously
     translated, or you don't know where to find the language pack for
@@ -54,7 +27,7 @@ ADDING NEW TRANSLATIONS
     make sure nobody has already created the translations for your
     language.  In the example below, we're going to create a
     translation for the mythical language "Fredonia" which has the
-    official language code of "ha".
+    official language code of "xx".
 
     In general you need to do two things to add translations for a
     language in Mailman.  You need to translate the message catalog
@@ -62,17 +35,17 @@ ADDING NEW TRANSLATIONS
 
     To translate the message catalog, grab the file
     messages/mailman.pot and make a copy called mailman.po in the
-    subdirectory messages/ha/LC_MESSAGES.  Then you edit the file and
+    subdirectory messages/xx/LC_MESSAGES.  Then you edit the file and
     add the translations for each message identified in the catalog.
     It will be very helpful to have a good tool, such as po-mode for
     Emacs, for this part of the job.
 
     Once you've added your translations, you can then run msgfmt over
-    your .po file to generate messages/ha/LC_MESSAGE/mailman.mo (it
+    your .po file to generate messages/xx/LC_MESSAGE/mailman.mo (it
     would also be a good idea to donate your translated .po file back
     to the Mailman project!)
 
-    Next, create the subdirectory templates/ha and translate each of
+    Next, create the subdirectory templates/xx and translate each of
     the files in templates/en/*.{html,txt}.  These you should also
     donate back to the Mailman project.
 
@@ -85,8 +58,7 @@ RESYNCHRONIZING THE CATALOG
     As Mailman development continues, new updated catalogs
     (i.e. mailman.pot files) will be made available.  As mailman.pot
     changes, the individual language catalogs
-    (i.e. xx/LC_MESSAGES/mailman.po files) need to be updated as
-    well.
+    (i.e. xx/LC_MESSAGES/mailman.po files) need to be updated as well.
 
     In general, I as the Mailman maintainer will merge the new
     catalogs with the individual language catalogs, and upload the new
@@ -94,16 +66,35 @@ RESYNCHRONIZING THE CATALOG
     mailman.po files from SF or CVS and update the translated
     messages.  They should also update the template translations.
 
+    For best results, you will probably want to keep current on
+    changes to Mailman 2.1 in the CVS.  As Mailman 2.1 moves towards
+    final release, the catalogs and templates should start to
+    stabilize.  Alternatively, occasionally I will make new English
+    language packs available on SourceForge, and you can use these to
+    create your translations.
+
 
 CURRENT LIST OF LANGUAGE SUPPORTED OUT-OF-THE BOX
 
     As of this writing (27-Jul-2001), Mailman 2.1alpha2 supports the
     following languages out of the box:
 
+    - Chinese (Simplified and Traditional)
     - English
-    - Spanish
     - French
+    - Hungarian
     - Japanese
+    - Spanish
+    - Norwegian
+
+    We've also had volunteers for these languages, although they
+    aren't yet integrated into the code base:
+
+    - Czech
+    - Dutch
+    - German
+    - Polish
+    - Swedish
 
     Hopefully more translations will be donated as Mailman 2.1
     development moves along.