comprehensive-rust/.gitignore

# Build artifacts
/book/
/exercise-templates/
target/
*.bin

# Translation artifacts
po/messages.pot
po/*.mo

# macOS artifacts
.DS_Store

# Jetbrains IDEs project files
.idea/
.iml
.iws
Italian translation: initial setup (#541) * Git-ignore Jetbrains IDEs project files * First commit of Italian translation file Just a few translations so far, to get things going. 2023-04-01 22:56:38 +01:00			`# Build artifacts`
Publish Comprehensive Rust 🦀 2022-12-21 16:36:30 +01:00			`/book/`
Add script to run exerciser on bare metal exercises. 2023-03-30 13:22:29 +01:00			`/exercise-templates/`
Add support for translations This implements a translation pipeline using the industry-standard Gettext[1] system. I picked Gettext for the reasons described in [2] and [3]: * It’s widely used in open source software. This means that there are graphical editors which will help you in editing the `.po` files. An example is Poedit[4], which is available for all major platforms. There are also many online systems for doing translations. An example is Pontoon[5], which is used for the Rust website itself. We can consider setting up such an instance ourselves. * It is a light-weight yet structured format. This means that nothing changes with regards to how you update the original English text. We can still accept fixes and PRs like normal. The structure means that translators can see exactly which part of the course they need to update after a change. This is completely lost if you simply copy over the original text and translate it in-place in the Markdown files. The code here only adds support for translations. They are not yet tested, published or used for anything. Next steps will be: * Add support for switching languages via a bit of JavaScript on each page. * Update the speaker notes feature to support translations (right now “Speaker Notes” is hard-coded into the generated HTML). I think we should turn it into a mdbook preprocessor instead. * Add testing: We should test that the `.po` files are well-formed. We should also run `mdbook test` on each language since the translations can alter the embedded code. Fixes #115. [1]: https://www.gnu.org/software/gettext/manual/html_node/index.html [2]: https://github.com/rust-lang/mdBook/pull/1864 [3]: https://github.com/rust-lang/mdBook/issues/5#issuecomment-1144887806 [4]: https://poedit.net/ [5]: https://pontoon.rust-lang.org/ 2023-01-08 13:45:19 +01:00			`target/`
Italian translation: initial setup (#541) * Git-ignore Jetbrains IDEs project files * First commit of Italian translation file Just a few translations so far, to get things going. 2023-04-01 22:56:38 +01:00			`*.bin`

			`# Translation artifacts`
Add support for translations This implements a translation pipeline using the industry-standard Gettext[1] system. I picked Gettext for the reasons described in [2] and [3]: * It’s widely used in open source software. This means that there are graphical editors which will help you in editing the `.po` files. An example is Poedit[4], which is available for all major platforms. There are also many online systems for doing translations. An example is Pontoon[5], which is used for the Rust website itself. We can consider setting up such an instance ourselves. * It is a light-weight yet structured format. This means that nothing changes with regards to how you update the original English text. We can still accept fixes and PRs like normal. The structure means that translators can see exactly which part of the course they need to update after a change. This is completely lost if you simply copy over the original text and translate it in-place in the Markdown files. The code here only adds support for translations. They are not yet tested, published or used for anything. Next steps will be: * Add support for switching languages via a bit of JavaScript on each page. * Update the speaker notes feature to support translations (right now “Speaker Notes” is hard-coded into the generated HTML). I think we should turn it into a mdbook preprocessor instead. * Add testing: We should test that the `.po` files are well-formed. We should also run `mdbook test` on each language since the translations can alter the embedded code. Fixes #115. [1]: https://www.gnu.org/software/gettext/manual/html_node/index.html [2]: https://github.com/rust-lang/mdBook/pull/1864 [3]: https://github.com/rust-lang/mdBook/issues/5#issuecomment-1144887806 [4]: https://poedit.net/ [5]: https://pontoon.rust-lang.org/ 2023-01-08 13:45:19 +01:00			`po/messages.pot`
Adds latest English changes to pt-BR translation (#396) * Adds latest English changes to pt-BR translation Updating latest changes in English version to pt-BR.po file using the `msgmerge --update po/pt-BR.po po/messages.pot` command. * Removes all `fuzzy` Removing all `#, fuzzy` lines so the translation can be live. 2023-02-14 17:43:00 +00:00			`po/*.mo`
Italian translation: initial setup (#541) * Git-ignore Jetbrains IDEs project files * First commit of Italian translation file Just a few translations so far, to get things going. 2023-04-01 22:56:38 +01:00
			`# macOS artifacts`
Adds latest English changes to pt-BR translation (#396) * Adds latest English changes to pt-BR translation Updating latest changes in English version to pt-BR.po file using the `msgmerge --update po/pt-BR.po po/messages.pot` command. * Removes all `fuzzy` Removing all `#, fuzzy` lines so the translation can be live. 2023-02-14 17:43:00 +00:00			`.DS_Store`
Italian translation: initial setup (#541) * Git-ignore Jetbrains IDEs project files * First commit of Italian translation file Just a few translations so far, to get things going. 2023-04-01 22:56:38 +01:00
			`# Jetbrains IDEs project files`
			`.idea/`
			`.iml`
			`.iws`