[Mailman-Developers] [Mailman-i18n] Updated message catalogs needed for Mailman 2.1.10

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 8, 2008, at 6:09 PM, Mark Sapiro wrote:

> If you are a language champion or otherwise responsible for a Mailman
> translation, please get the updated 2.1.10 message catalog for your
> language to me as soon as possible. Mailman 2.1.10 has been in beta  
> for
> 3 months now, and I have received very few updated translations.
>
> I am planning to release what I hope will be the final beta release of
> 2.1.10 in a few days. This would be a release candidate rather than a
> beta if I had more updated translations.

I think it may be time to once again consider modernizing our i18n  
workflow, especially for 2.2 and 3.0.

Let me state up front that I'm HUGELY grateful for all the excellent  
work that the i18n volunteers have contributed over the years.   
Through your work, Mailman was one of the first localized Python  
projects and we invented a lot of the basic Python machinery for  
internationalizing applications.

Of course, things have come a long way since then, and I think it may  
be time for us to join a wider translation community.  AFAIK, the two  
leading contenders are running our own Pootle service, or using  
Launchpad translations.  Is there any other viable alternative?

I'd like to get some feedback from the current i18n volunteers to see  
what you think.  If you believe that the status quo is best, feel free  
to say so.  I think it's not, but I'm open to opinions.  What I'm  
really looking for is a system and process that makes both the  
translators lives better, and doesn't put blockages in our workflow  
for releasing new versions of Mailman.

Thanks,
- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkfVTPYACgkQ2YZpQepbvXFi2QCfUXfgKcktYHrtEODoxd07Xsft
ZH8AnRvkLxP92KZL24bFja+C96/22FYO
=lF7M
-----END PGP SIGNATURE-----