-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use po files #19
Comments
@JulienPalard hi! I'm one of the maintainers of this translation and we try to keep it always updated. We have online the 3.6 version of the official tutorial, which is the latest one. We don't translate all the Python documentation, only the tutorial. I would like to expose the po files so you can build this tutorial also, but I will need some help on the process. Please, let me know where I can read more about this or if you have time to chat/talk. Thanks, |
Hi, You can read more about our current work here: https://www.python.org/dev/peps/pep-0545/. The typical process we use to translate the documentation is, in broad lines:
This process is shared by all translations but each of use automate this with our own tools as we still not shared this, for french translation we use a Makefile. In this process, as we all work with We're also synchronizing our Are you using po files too, internally or are your translating rst docs? html docs? |
Hi, I'm Julien, the french translator of Python.
I'm working on python/docsbuild-scripts#8 to build each translations of the python documentation, we currently have japanese, french, and chinese.
We would be able to build your documentation too if you expose po files in your repository. If you want to do it, consider "gettext_compact=0" (used by fr, ja, and zh-tw) and maybe join the common transifex project: transifex.com/python-doc/.
You can still use any hierarchy you want, there's still no guidelines about it:
Docsbuild script is compatible with this three possibilities.
The text was updated successfully, but these errors were encountered: