Figure out process for translating guide to other languages

[yuvipanda]

We should translate TLJH into lots of languages. There are several challenges to be overcome here:

1. How will commit rights work? A lot of the current maintainers do not actually know non-english languages, so we should figure out a process for how this works.
2. How to make sure things are accurate? When we add new content or fix bugs in our current content, we need to make sure that either other languages are updated, or there's an easy way to flag that this has changed.

This is very important work, and we should spend time and effort on it!

https://docs.readthedocs.io/en/latest/localization.html is some info on how RTD does localization.

[henfee]

Yes, it's very important to help other users no speaking English.
I had tried to do this by translating jupyter notebook UI from English into Chinese a few months ago, as
nootbook_i18n_Chinese

[consideRatio]

I'd love to share the enthusiasm, but I don't think we should translate TLJH to multiple languages =/

I'm afraid non-english speakers will be better off with automatic translation tools like google translate than to rely on manually translated sections of our docs. My assumption is that manually translated docs is only better if they have good coverage and are well updated, but I don't think we can accomplish that.

For reference, consider jupyter/docker-stacks and jupyter/docker-stacks#1489. The documentation is currently available in a very partial capacity in multiple languages: https://jupyter-docker-stacks.readthedocs.io/

Related

• Translating docs to Spanish #188