bazel-contrib / bazel-contrib/rules_python

sphinxdocs: i18n support

Ouverte
#3,848 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
sphinxdocs type: feature request
Langage dominant
Starlark
Étoiles
688
Forks
721
Merge moyen
15 h 7 min
PR mergées (30 j)
76

Description

# 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

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Domaine
build-system, documentation
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
Plutôt claire
Accessibilité débutants
48/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.