Hi all, During Djangocon in Portland I had the chance to talk to Malcolm and Russell about how we might be able to improve contributing of translations of Django, because of the weak points of the current workflow, for both translators and committers:
- monstrous patches, which the committers can't actual check for correctness - incomplete or unmaintained translations - complicated process for new languages and translators That's why we propose to start using Transifex [1], which is "[..] a batteries-included, common, upstream translation service, allowing people to collaboratively translate software, documentation and other types of projects." While not all details of how we are going to use it are worked out, and a bigger update to Transifex is about to land [2], we'd like to know from you -- the translators -- if there are any specific blockers we aren't aware of, that we need to work with the Transifex developers to make it work for us. So if you happen to have used it before or would be so nice to try it out for one of the existing projects, we'd be happy to make the switch for the next release. I currently have a read-only project setup on Transifex.net for Django [3], that you can browse, but I'd also happily setup a writing test project for anyone wanting to try it out. But of course any other real project would be happy for your translation help, e.g. other Django apps [4]. If there are any questions, please let me know, Jannis 1: http://transifex.org 2: http://trac.transifex.org/wiki/Development/Transifex-1.0 3: http://www.transifex.net/projects/p/django/ 4: http://www.transifex.net/search/?q=django -- You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to django-i...@googlegroups.com. To unsubscribe from this group, send email to django-i18n+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-i18n?hl=en.
