Translation project of Rust documents
I previously proposed adding a subrepository for translating documentation to Rust, but it was closed due to lack of capacity to maintain it on an ongoing basis.
Add submodule for document translation
rust-lang:master ← dalance:translations opened 03:23AM - 28 Nov 24 UTCdalance +64 -0
This PR adds a submodule for document translation. ## Motivation Now transla…tion DBs are placed at the each document repositories (e.g. rust-by-example). This causes to increse merging cost of translation update by document maintainers. Instead of it, the merging cost can be reduced by splitting the translation DBs to another submodule. I tried to gather feedback about this idea through Internal Forum and Zulip, and I create this PR because there was no feedback. https://internals.rust-lang.org/t/pre-rfc-translation-sub-repository-for-rust-docs/21666 ## Summary of this PR This PR adds the following steps to bootstrap build of doc. * Copy css/js for language picker to the theme directory, if there is a translation DB for the processed doc,. * Set `po-dir` to specify the translation DB in the translation submodule. * Build translated docs (this is already added) * Cleanup the copied css/js files to keep the repository clean. ## TODO This PR is incomplete yet. If this is acceptable, I think the following items should be done before merging this PR. - [ ] Move the submodule into rust-lang organization - [ ] Write README.md of the translation submodule - [ ] Follow other rules for submodule of rust-lang/rust - [ ] Remove modified `index.hbs` from rust-by-example ( because it conflicts with this PR ) - [ ] Remove language entries directly written in `src/bootstrap/src/core/build_steps/doc.rs` and add a mechanism to refer the entries from the translation submodule
So, my other idea is to set up a GitHub organization (e.g. rust-lang-translations) and domain (e.g. rust-lang-translations.org) for translations, and centralize all documentation translations there.
If this proves that there are sufficient translation resources, we can use that as a basis to consider merging it back into Rust itself,
but if no one joins, we can conclude that there was no demand for translations in the first place.
If you have any thoughts on this idea, please let me know.
Translation project of Rust documents
documentation
I previously proposed adding a subrepository for translating documentation to Rust, but it was closed due to lack of capacity to maintain it on an ongoing basis. So, my other idea is to set up a GitHub organization (e.g. rust-lang-translations)...
Source: View source
