New project : docs.python.org/fr/

Hi!

We're translating https://docs.python.org in french since around 2000. After using pottle for a few years, since 2015 we only use git & github to translate.

While it works for us because we're willingly using translation to teach git and contribution to open source software, it does not fit everyone: some would just like to translate.

Please note that other languages translators of docs.python.org use various systems to translate: they're all free to choose their process, and we're not going to force them to change, I hope translatewiki has the ability to choose a set of language to translate to.

We do use `.po` files (it's a Sphinx), it's 53034 entries as of 2021-03, 22879 are translated (~43%), and the repo is public on github: https://github.com/python/python-docs-fr, license is CC0, and it change from time to time, mainly on cpython version bumps (yearly), but contributions to upstream docs can occur daily.

We do have a huge proofreading (grammar, spelling, typos, semantic, ...) step before merging a pull request, I would not like translators to use translatewiki as a way to bypass the proofreading step, but I don't know how it can be "integrated".

What I can imagine is: we could take translation from translatewiki and make them PRs so we can review them, edit them at will, before merging, but it would require our modifications to be pushed back to translatewiki to avoid getting out of sync... I don't know what's possible here.

What do you think?

Mdk (talk)‎

Hi Mdk,

Thanks for your interest in using translatewiki.

The translation system at Translatewiki.net is designed to translate software projects into various languages from the source language but as far as I understand it, you'd like to just allow translations to French for https://github.com/python/python-docs-fr

Additionally, I see many .po files in the repo here: https://github.com/python/python-docs-fr which I assume is for individual pages? Everytime a new file is added there we'd have to make some changes to the configuration to read that file on Translatewiki and allow translators to translate them.

Considering the above, and the fact that our UI is not very well suited for translation of long form text, I don't think that translatewiki is a good fit.

To give you an example of how things work, see the following project: https://github.com/WPCleaner/wpcleaner/tree/master/WikipediaCleaner/src/org/wikipediacleaner/translation

Here we read the WikiCleaner.pot file and then identify what strings have to be translated, and allow translators to translate the strings to different languages. You can see the corresponding ".po" files. This is then submitted out to the GitHub repo via a PR: https://github.com/WPCleaner/wpcleaner/pull/61 which the maintainer merges.

Regards,

Abijeet Patro (talk)‎