Closed michaelweinold closed 2 months ago
If I might be so bold, @tngTUDOR : What is the real case for this? My main concerns:
Introduction
, LCA
, FAQ
)?yes, I was thinking specifically about the "explanations" pages themselves. @michaelweinold can you point me to what you mean by "browser translation" ?
can you point me to what you mean by "browser translation"?
...maybe as additional food for thought:
How would we ensure that contributions such as eg. https://github.com/brightway-lca/brightway-documentation/pull/118 are propagated to the other-than-English branches?
Would we auto-translate those (in which case, 👀 browser translation) or would we need to set up a strategy that assigns language experts (from the Brightway developers?) to these PRs?
Closing this for now - localisation of the entire (or part of) documentation would be a major effort that should only be undertaken after the English-language content of the documentation has been expanded/consolidated.
At the request of Brightway resident linguist @tngTUDOR work is to commence to add multi-language functionality to the Brightway documentation.
As luck would have it, I recently came across this PR in the
pydata-sphinx-theme
repo related to a project that uses translations heavily:Perhaps we could take some inspiration from their setup.