Jordi Mallach brings up a good point on the rosetta-users mailing list,
in response to my queries there.
Rosetta doesn't really work with non-po files, so the fact that we have
templates that need translating will cause us some grief. Well, even
more grief than it has over the years. ;)
Does anybody have any good ideas for handling this in the Mailman 2
tree? For MM3, it's a top priority that any templating system we use
must support po-ification for i18n. For Mailman 2.2 it's more difficult
because I don't think we should adopt an entirely new template system.
It's even worse for 2.1 because we're not accepting new features,
although if we came up with something simple and minimally disruptive,
I'd consider it for the benefit of improving the translation process.
Ideas are welcome!
In what will hopefully be just the first of several improvements to the
Mailman development process, I would like to get some feedback from the
i18n developers on moving translation coordination to Rosetta.
Rosetta is part of Ubuntu's Launchpad and while I haven't played around
with it too much (problems with my ancient gpg keys I suspect ;) it
looks a lot like what a few of us dreamed of writing several years ago
(but of course, never did). Rosetta is essentially a web based
interface for translating open source applications. The site has the
potential to be a much better collaboration platform for translations
than the mailing list or my inbox. It also looks like it would open us
to collaborating with a much larger i18n community.
The ultimate goal of course is to continually improve the quality and
breadth of Mailman's translation. The current set of champions have
done a great job getting Mailman i18n to where it is now, but I think
that something like Rosetta can make all our lives easier.
Specifically, I think Rosetta could help eliminate me as a bottleneck,
or require translators to deal with all the nastiness of committing
updates to the CVS trees themselves.
I would like to get feedback from the current i18n champions on this
plan. If you have experience with Rosetta, both positive and negative,
as a translator or developer, I would be very interested in hearing your
For more information see: