During the italian translation of Mailman I've done many typo errors
which, in the worst case, caused Mailman misbehaving. I think the
real problem is that I couldn't find any editor or tool which does
the following checks:
- when translating a text template, if a given %s or %(var)s is
in the original file it probably should appear the same number
of times in the translated text.
- in the translated text you shouldn't have a %(var)s if that
%(var)s wasn't in the original text.
- when translating an html template, the same concept should
apply for <MM-*> tags.
- when translating the .po file, the same concept should apply
for each msgid/msgstr pair.
So, to easy the process, I've written a small script to check my
translation whenever I do some update. This script has been
generalized and now you can use it for your language too.
Just for an overview of how much the tool can be effective, this
simple bash script:
for i in big5 cs de es fi fr hu it ja ko no ru;
echo -ne "$i:\t";
transcheck -q $i;
applied to the last Mailman-CVS has reported:
big5: 33 warnings in 9 files
cs: 192 warnings in 3 files
de: 136 warnings in 6 files
es: 115 warnings in 12 files
fi: 312 warnings in 6 files
fr: 58 warnings in 4 files
hu: 105 warnings in 6 files
it: 1 warnings in 1 files
ja: 182 warnings in 3 files
ko: 231 warnings in 8 files
no: 30 warnings in 3 files
ru: 341 warnings in 13 files
Before using my script, the italian translation counted about 70
warnings. The one still counted actually is not an error: a
%(var)s appears two times in the original english text but in
italian we have intentionally only one.
Using the script without the -q switch, you can see a detailed
The script isn't perferct and can be improved in many ways:
- better regexp to search for Python %(var)s
- better .po parser
- better exception handling for strange situation
- generalizations to use it in other python projects
but it's already good (at least for italian).
Feel free to use it and to report any feedback.
Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo
I'm currently looking for the dutch translation pack for Mailman, as
stated onthe website:
The site administrator can install new language packs as donated by volunteer
translators. If you'd like to volunteer to help with translations, or
would like todownload language packs for installation at your site, please contact the
mailman-i18n(a)python.org mailing list.
So i would like to request the dutch language pack
I would like to download de portugueses translation pack? Where this pack
Rodrigo Brasil do Couto
Fundação Getulio Vargas
DITI - Divisão de Tecnologia da Informação Tel.: (0xx21)
Setor de Suporte de Redes
Fax: (0xx21) 2559-6009
If now one else has volunteered to take that job before, I would like
to work on the Estonian translation/language pack for Mailman.
A little background information about me: I have previous experience in
localizing gettext based applications. I'm part of KDE's Estonian language
team, where the localization of programs the kdegames module is my
responsibility. I have also worked on unofficial translation of
Majordomo and a number of other smaller programs.
Currently I am also administrator for 2 small Mailman installations,
which run 30 and 10 lists respectively.
Based on that, I believe that I have the necessary knowledge and skill for
this job. I have a pretty clear picture of what is involved and I'm all
set up for it; all I need is an OK from you.
 unofficial, because it didn't have any support for gettext or
similar internalization libraries and therefore translating it ment
changing the code directly.
I've got Mailman 2.1.b1 installed, and I was wondering about
international (specifically Japanese) characters in the subject line.
When recieving via e-mail (and viewing with a capable e-mail client),
the subject line, text, etc are all displayed correctly. As a test, I
put a few kanji in the title and message body, and hopped over to the
archives. The kanji/japanese in the body showed up just fine, but the
subject line became this:
Is this a known bug/work in progress, or is there something I can change
to fix it?
gary c wang