switch to external translation system

[Sumana Harihareswara]

Finish the transition to an externally managed translation system. This is necessary for the Mailman 3.0 release.

Right now someone has to send new translations to Mark and he has to do a new release with new catalogs; see http://wiki.mailman.psf.io/DEV/Internationalization and http://wiki.mailman.psf.io/DEV/i18nhowto for more info. We have some notes at http://wiki.mailman.psf.io/DEV/Managing%20Translations about what we want in the future. It must be free software (this is why we cannot use Transifex).

The workflow Barry would love: a developer can develop their software, marking all strings for localisation. Someone can take the trunk branch and run a tool to extract all the strings and provide Mailman developers with GNU gettext catalogs, or make them available in a branch, or on the web, so Mailman maintainers can check them out.

There exists enough distributed machinery that we should be able to do this in a disconnected way.

(From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series.)

[Aurélien Bompard (abompard)]

I would like to mention the existence of Zanata <http://zanata.org/> which is 100% Free software. Could we use that?

[Barry Warsaw (barry)]

On Apr 10, 2015, at 07:42 PM, Aurélien Bompard wrote:

>I would like to mention the existence of Zanata <http://zanata.org/>
>which is 100% Free software. Could we use that?

At least the license looks pretty decent, being GPL'd. I've just signed up
and will try to create a Mailman project once I get the confirmation email.
Then we can at least play with it and see if it'll do the trick for us.

[Abhilash Raj (raj-abhilash1)]

This bug has been moved to the new gitlab repo here: https://gitlab.com/mailman/mailman/issues/85