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!
-----BEGIN PGP SIGNED MESSAGE-----
Is there an Arabic translation on the work for mailman? If not, then I can
volunteer to maintain it.
Can you point me to the proper procedure or any relavent doc, please?
Telecommunications and Electronics Engineer
Maintainer of Fedora Arabic Translation Project
Maintainer of the OpenBugs project page at
Master CIW Designer, ICDL, MOUS, Linux+, LPI 101
New Horizons CLC, Riyadh, SA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
-----END PGP SIGNATURE-----