Hi, On Sat, Apr 28, 2012 at 21:50, Barry Warsaw wrote:

- translatewiki.net. Pros: open source (I think),

GPLv2 or later. But a lot of what you get by using TWN is not in the software itself, but in the community and staff that exists on the site. If you run your own copy you won't necessarily get the same kind of community and staff to go with it.

had some discussion with their developers back in January. Cons: is wiki a good fit for translating Mailman?

Why not? ;) I don't do any translation myself and have only used the interface for ~5 mins over a month ago so read with grains of salt. (i.e. I may be saying something false or wrong) It is a wiki and the strings are stored as wiki pages. It might be possible to edit those strings as individual wiki pages, I'm not sure. But there's an ajaxy, dynamic interface for translators and surely the vast majority of online translations use that. (there's also the option to download strings in bulk and do translations with an offline tool and then automatically import them to the wiki. but online translation is preferred to offline and I think is more commonly used. anyway, if for some reason a particular user doesn't like the web interface they might be able to continue using the same tools they use now for the actual translation, just the checkout/checkin process would be different) You should talk to some of the existing users of TWN directly to see about their experience with it and get some of the existing mailman translators to try it out with any project that already uses TWN. (just register and do some translations for an hour)

May have some problems ensuring FSF requirements for contributions.

I discussed this with the FSF again on Tuesday (6 days ago). There's been some progress off and on with getting the FSF to approve the use of TWN. Was stalled recently because there were other things distracting them but now they're working on it again. I should have another update from them within ~8 days from now. -Jeremy