-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Multilanguage support and GitHub Actions #3829
base: rolling
Are you sure you want to change the base?
Conversation
306d45f
to
c30c451
Compare
I have finished the configurations. Now I just have a few considerations:
|
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/translation-of-ros-industrial-training/33239/1 |
With gettext, it is posible to avoid translating twice the same content (see locale/es/LC_MESSAGES/Installation.po:1160)
As discussed in #3249, the support for multiple languages is a barrier that we can eliminate in the ROS learning curve. To address this, I have put forward a solution in #3678, building upon the feedback from the previous issue and as discussed with @clalancette. I am opening this PR for review, and I welcome any suggestions or comments to further enhance the proposal.
Process
To translate
rst
files, some tools are used following the following process:This process can be somewhat simplified with the help of the
sphinx-intl
library:.rst
files with the documentation in English..pot
file from the.rst
files usingmake gettext
(these files would be stored in thebuild
folder)..po
files with the.pot
files usingsphinx-intl update -p build/locale -l <language>
..po
files manually or with the assistance of a translator.make -e SPHINXOPTS="-D language='<language>'" html
(the output would be stored in thebuild/<language>
folder).File handling is better described in #3678, but I am still willing to answer questions or concerns in this PR.