🚀 Deployed on https://6391f2b826d33a1b33715b9c--scverse-tutorials-doc-preview.netlify.app

This is a draft for Internationalization.

This is currently a 4 step process:

1. First, run sphinx-build -b gettext . _build/gettext from the 'docs/' directory. This tells sphinx to parse your files and automatically find a bunch of strings-to-be-translated and give them a unique msgid.

2. Next, we tell sphinx to prepare some X (in this case 'de') destination-language '.po' files from our above-generated '.pot' files. sphinx-intl update -p _build/gettext -l de

3. These language-specific '.po' files are where we actually do the translating.

4. Build html for language (in this case 'de') make -e SPHINXOPTS="-D language='de'" BUILDDIR="_build/html/de" html

Open issues:

1. Translation of ipynb files is not trivial, sphinx-intl expects the cells as json.
   A possible workaround would be to convert the .ipynb file to .md, rename the .md file (must not have the same name as the .ipynb file) and then run the gettext command.

2. Add a language picker to the index file.

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

Powered by ReviewNB

Translation of ipynb files is not trivial, sphinx-intl expects the cells as json.

What do you mean? Aren’t the cells json?

I’m very much not a fan of making things complicated by adding support for some magic Markdown dialect. Let’s stick to standard .ipynb files.