bazel-contrib / bazel-contrib/rules_python
sphinxdocs: i18n support
- Lingua principale
- Starlark
- Stelle
- 688
- Fork
- 721
- Merge medio
- 15h 7m
- PR unite (30g)
- 76
Descrizione
# sphinxdocs: i18n support
### Relevant Rules
`sphinx_docs` in `//sphinxdocs/sphinxdocs/sphinx.bzl`
### Description
`sphinx_docs` should accept a `lang` array of strings and produce docs for each specified language
### Describe the solution you'd like
per https://www.sphinx-doc.org/en/master/usage/advanced/intl.html I think it would have to run `sphinx-build gettext`, save the `.po` files somewhere within the repo (pretty sure that these are checked into the VCS), and then run `sphinx-build -Dlanguage=` for every specified lang
### Describe alternatives you've considered
`sphinx-intl` seems to be the common extension for i18n workflows but it doesn't seem strictly required https://www.sphinx-doc.org/en/master/usage/advanced/intl.html#translating-with-sphinx-intl
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by reading the `sphinx_docs` rule in `//sphinxdocs/sphinxdocs/sphinx.bzl` and the linked Sphinx internationalization workflow. Done means the rule accepts a `lang` array, generates translation files as needed, and produces documentation for every specified language.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Ambito
- build-system, documentation
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 48/100