Offer: Change Internationalized Manual from parallel content en, de etc. to i18n sphinx_intl

[acsr]

I have created a sophisticated Sphinx workflow for i18n based translations for Sphinx manuals for the manual of the VR-Suite Software we use in another project.

It is based on an enhanced makefile and a corresponding build environment for SublimeText 3.
We use OmniMarkupPreviewer Plugin for a quick live preview on ReST level to check the look and feel but misses some special directives from Sphinx exclusive markup like references and link creation.

We use 5 steps to trigger make gettext, make rebuild_po, make i18nstats, make compile _mo and make html_intl.

Finally you can add make publish to upload via rsync to the webserver.

You can click build errors/warning in the console of SublimeText and it takes you directly to the source location and displays the errors inline in the code.

Alternatively I have the same as a build environment under testing inside of Visual Studio Code, which has the benefit of live rendering changes with a small delay in the source as actual Sphinx in a browser based split window of the editor.

Interested to distribute the task of writing of the manual to non developers and professional translators? I can help to set it up. (The docs for this are currently in a private repo, that I cannot share easily.)