I committed updates to the Mailman catalogs for 2.1.5. You should be
able to CVS update and update your translations. I probably won't have
time to release 2.1.5 until after Pycon so you have some time to update.
Don't forget: you definitely want to be working on the Release_2_1-maint
branch. In your CVS checkout, be sure to do:
% cvs -q up -Pd -r Release_2_1-maint
to get the latest copies.
I am a systems administrator at Hacettepe University, Turkey. We have lately
migrated from Majordomo to Mailman and are happy to say that we quite loved
When I downloaded Mailman, I looked if there was a Turkish translation for
it, and saw that, while it seemed like it is being translated (not
submitted), there was no translation. I have been translating and using it
for more than two months, and as still nothing has been posted for Turkish
translation, I decided to post my translation for production use.
Attached is the Turkish translation for Mailman 2.1.4
I am also the head Turkish translator for the SquirrelMail webmail project,
so I think my translations should be highly reliable :-)
If there are Turkish users in your mailing lists, please enable Turkish and
send any feedback from them to me.
Best regards to all users and developers of the project.
Hacettepe University, Computer Center
On Tue, 2004-03-09 at 20:29, Barry Warsaw wrote:
> I'd like to get 2.1.5 out before Pycon and I think there are enough
> significant changes to warrant getting it out asap. Also, a few things
> have clicked in place recently and I need to start the MM3 Pycon sprint
> discussions this week.
How about generating the .pot file and announcing string freeze on the
Release_2_1-maint branch at least a week or so before 2.1.5 makes its
way out the door?
Then translators will have time to update their translation. :)
Translators: Is one week enough? :)
in the most up-to-date messages.pot appears the following line :
msgid "Edit Options"
however, in the parsed HTML page the caption of the button reads "Unsubscribe or edit options". Which one is correct?
And a bit off-topic: IMHO, the names of the languages at the listinfo and roster pages should be in the national language - in contrast to the admin section where they should be in the interface language (the admin should know which languages he enables, shouldn't he?)
The idea is that the visitor can change the language of the interface to his convenience, but once the names appear in some other lingua - how should he guess? Extreme example: a mailing list where all discussions flow in Volapük however the owner enables his diverse audience enjoy interface in several other languages - Danish (dansk), French (français), Thai (ไทย), Russian (русский). Furthermore, he himself is from Japan so the default is Japanese. A visitor coming to the site would have no idea how to make it readable and even if he manages to find the combo-box, what would he select? All language names are in Japanese!!