On Sat, Dec 15, 2012 at 11:53 AM, Amirouche B. <amirouche.boube...@gmail.com > wrote:
> Héllo, > > Everything is in the title. Does Django core dev's want to have localized > documentation in main repository or should it be managed by local DUG ? > Yes :-) In a perfect world, you'd be able to get documentation in other languages on docs.djangoproject.com. If you look at the URL space, you'll see that we've already prepared for translations -- you hit /en/dev to get the development docs; in theory, we could serve /fr/dev for french documentation. However, what we're missing is the process for managing these translations. The core team speak a few languages (we've got German, French and Spanish covered, and possibly a couple of others), but aren't in a position to review and commit revisions for lots of other significant languages. Taking i18n and l10n as an example; we've moved to using Transifex specifically because it allows us to give control of translations to local language communities; then, once per release, we push a single commit of translation updates to the main repository. Ideally, we'd take a similar approach for translated docs, but Transifex isn't really well suited to translation of large bodies of text. So - your translation efforts are definitely welcome. What we need to work out is the process by which we can practically use these translation efforts -- and, more importantly, make sure that they're kept up to date (e.g., once a base translation is done, ensuring that translation teams have a 'todo' list, and we can indicate to readers which translations are current, and which are stale). Any suggestions on how we could manage this are also welcome. Yours, Russ Magee %-) > Thanks to Pilot Systems, I improved a bit the french documentation > [1] basically what I've done is converted it to use the Sphinx support of > .po files and translated the how-tos. > > Now what main repo needs: > - fix the Makefile [2] like it's done in [1] or something smarter maybe > convert the Makefile to a Python script so that we have a better handling > of locales please see [2] > - the source documentation needs some fixes to be fully possible to do > L10N but it's not a priority (problems might be solved in Sphinx) > > Mind the fact that getting .po support and the facility to do > documentation L18N in the main repo is needed to avoid any future effort to > do what is IMO a mistake to translate the documentation in the rst files. > > What do you think ? > > > Thanks. > > > [1] https://bitbucket.org/amirouche/django-fr-translation > [2] > https://bitbucket.org/birkenfeld/sphinx/issue/1026/makefile-for-building-mo-and-merging-po > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/r5vbKm3wovEJ. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
