Hi Mathieu, > I've jsut read your email about the translation of Django and i was > curious to ear a little bit more about it. > > Let me just introduce myself. I'm part of the organizer team of > Montreal-Python and i work mostly with django. Since a couple of > months we, at MP, are organized sprint to help to translate the > documentation of Django in French.
Very cool, that could be a case for i18n'ed Sphinx... ah :) > When i saw your post, i became curious to know if you were talking > about the translation of Django itself or also the ref documentation. > It would be very cool to have a complete translation infrastructure > for the doc but right there's no many thing in place. Indeed, this is orthogonal to the translation of Django, but Transifex would certainly be a good tool to handle it. Have you made any attempts in using Transifex (or even better, the new string based beta.transifex.net)? > Maybe you head about the sphinx-i18n project. Indeed, I tracked Robert's progress over the summer (which was gladly mentored by Martin von Löwis and Georg Brandl, and a little bit by me). Daniel Neuhäuser's work on versioning translation strings was also a big step forward for translated docs. > It's GSOC project with > goal to develop a way to generate .po files from rst files and than > being able to maintain correctly the translation of a complete > documentation. > > https://bitbucket.org/lehmannro/sphinx-i18n/src > > Is there any plan to use or implement something like this in django ? Yes, Martin and me have talked a lot about exactly that during Europython -- and I'm seriously thrilled about those new possibilities. But kickstarting the official documentation translation process is a lot more complicated than the already existing translations, e.g.: - Sphinx' PO builder hasn't been released yet (will be as part of Sphinx 1.1) - the Django docs app needs to be updated for the new way of building documentation on the Django project server. I've started this, but got distracted by the upcoming Trac update during the Djangocon sprint. The server will soon be updated by Jacob, which I'd want to wait for, too. - given the sheer amount of strings in each PO file, which Sphinx' PO builder would generate, there is no way we can handle that without Pootle or Transifex; but how does Transifex behave with so many strings? Do we need to modify it for such a project? - Updating the contributing documentation with terms for docs translation In other words, we have a few open questions which we need to deal with before we can get started. I definitely think we can work on some of them now, if anyone wants to help out. But that's also why I think test-driving Transifex for the translation of Django is a good first step towards getting to know the workflow and finding the hurdles. > The python documentation is currently being translated with it: > http://pootle.python.org/pootle Indeed, which btw is another Django project nowadays, yay! :) Jannis > On Sun, Sep 19, 2010 at 6:46 PM, Jannis Leidel <jan...@leidel.info> wrote: >> 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. -- 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.
