Barry Warsaw writes: > There is some validity to the complaint that new releases are blocked > on translation updates. Our translators do a wonderful, and greatly > appreciated job, but they're disadvantaged by our suboptimal > translation process.
Fixing that won't help security releases, though. I don't recall anybody waiting on translations for the Apache traversal bug. > I think we also need to find a better way to package non-English > language support so that updates to languages can happen on their > own schedule without requiring or blocking the core Mailman > releases. How do you propose to do that, except by releasing English-only versions first? I don't know the details of Python's implementation, but the gettext C library is already pretty close to optimal on this, isn't it? You just drop a random .mo file into the right place, and gettext will use the translation it finds if there's one there, and otherwise spew the original string. So all you really need is a utility to uninstall (and optionally back up) the old language file and install the new one in the right place. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
