aboutsummaryrefslogtreecommitdiffstats
path: root/README-I18N.en
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--README-I18N.en98
1 files changed, 71 insertions, 27 deletions
diff --git a/README-I18N.en b/README-I18N.en
index b3efcd64..1f3c2432 100644
--- a/README-I18N.en
+++ b/README-I18N.en
@@ -132,33 +132,77 @@ DONATING YOUR TRANSLATION BACK TO MAILMAN
CURRENT LIST OF LANGUAGE SUPPORTED OUT-OF-THE BOX
- As of this writing (23-Dec-2002), Mailman 2.1 supports the
- following languages out of the box:
-
- - Czech
- - Chinese (Simplified and Traditional, but may have problems)
- - Dutch
- - English
- - Estonian
- - Finnish
- - French
- - German
- - Hungarian
- - Italian
- - Japanese
- - Korean
- - Lithuanian
- - Norwegian
- - Portuguese (Brazil)
- - Russian
- - Spanish
- - Swedish
-
- We've also had volunteers for these languages, although they
- aren't yet integrated into the code base:
-
- - Catalan
- - Polish
+ See http://www.list.org/i18n.html
+
+
+MORE INSTRUCTIONS
+
+ Here is the recipe that Simone Piunno used for the Italian
+ translations:
+
+ "You can start without much technical knowledge, but if you want
+ to keep your translation up-to-date (while the development branch
+ evolves into the next stable release) you'd better learn how to
+ use cvs and diff.
+
+ Here is my recipe.
+
+ Basically, you'll start by copying templates/en/* to your sandbox dir
+ and then translating each file. Keep in mind that %(foo)s is a
+ variable reference (much like %s in C) and must be left untouched.
+ Also, you must be able to recognize a markup tag (eg, <foo>) because
+ they must be left untouched too, and you should know how to escape
+ non-ASCII characters, e.g. "è" -> "&egrave;", but only in html files.
+ Remember that if you need a literal % sign, it must be doubled: %%
+
+ Next, you copy messages/mailman.pot, renaming it to serbian.po.
+ You can open this file with kbabel (a tool included in KDE SDK) and
+ translate each string (original on the higher half of the window, your
+ translation on the bottom half).
+
+ If you are a masochist, you can even use emacs PO mode ;)
+ Keep attention to the same markers and escaping as above, with the added
+ complexity that here it's harder to say when a string is html (e.g. used
+ for web UI) or pure text (e.g used for email interface)
+
+ Then you try to compile you .po file:
+
+ msgfmt -v -o serbian.mo serbian.po
+
+ No error messages should appear.
+
+ Next, copy your files on an installed mailman tree, and run
+ bin/transcheck XX, where XX is your coutry code.
+
+ No warning should appear (but maybe some warning is ok, if you really
+ know what you're doing).
+
+ Now, try to run your translation (add an "add_language" line to
+ Mailman/Defaults.py) and check the many scattered pieces blend
+ together well. Sometimes you'll need some adjustment.
+
+ When you're satistied, pack up a tar.gz with the following structure:
+
+ messages/XX/LC_MESSAGES/mailman.po
+ messages/XX/LC_MESSAGES/mailman.mo
+ templates/XX/admindbdetails.html
+ templates/XX/admindbpreamble.html
+ .
+ .
+ templates/XX/userpass.txt
+ templates/XX/verify.txt
+
+ (XX is your country code) and send it to Barry Warsaw.
+
+ By that time, your translation could be somewhat obsolete, because
+ templates and mailman.pot could have been evolved meanwhile.
+
+ Don't panic.
+
+ You'll need to check diffs to find what changed and how, so that
+ you can easily update your files.
+
+ Save everything everytime, you'll need it.
MORE INSTRUCTIONS