* Update match-expressions.md
* Apply suggestions from code review
Fine tuning the casing and explanations.
---------
Co-authored-by: Martin Geisler <mgeisler@google.com>
* fix: korean translation for day2
This covers 12, 13, 14 in TOC.
* Refine ko-translation regarding match with enum
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* Suggesting to add `Default` to important traits.
This is a great trait to know about, it is used very often.
* Change `Implemented` to tuple struct.
It saves vertical space.
This makes `mdbook` output a simple redirect at the location of the
old pages. I’ll try to add such pages when we shuffle around our
pages to make sure external links stay valid.
* Add Brazilian Portuguese translation
Adds Brazilian Portuguese translation. Day 1 is respectable and the most glaring machine translation errors are removed throughout. There will of course be exceptions at this early stage.
Conventions: followed standards of the Rust Book translation at https://rust-br.github.io/rust-book-pt-br/
for guidance on Anglicization of programming vocab.
Generally where words refer to a type, method etc in Rust, I switch the translation to English (eg 'Enum', 'read') and stick to the Portuguese when the word refers to an abstract concept (eg shadowing, sombreamento).
The entire 20k lines have been parsed to remove all over-eager translations, many of course of which were in the code blocks ('let mut x / deixe mut x).
Variable / struct names (eg Pessoa -> Person) have been translated so the code runs, comments and some print statements are left in Portuguese.
Assistance welcomed!
* Update pt_BR.po
* Move Cargo.toml for exercises to exercises directory.
* Create a workspace with both exercises and i18n-helpers.
* Build in CI as well as testing.
* Binaries must have a main function.
* No need for workspaces configuration for caching anymore.
The code is probably meant to illustrate the `vec!` macro, but it
feels out of place when teaching: there is already enough material
here to get through.
* Update unsafe.md
Adding a paragraph explaining that unsafe code is not necessary broken or evil, but it is a mode
where compiler safety features are off.
* Move explanation to speaker notes
To avoid slide being too long. Also edited text slightly.
* Remove extra space
---------
Co-authored-by: Andrew Walbran <qwandor@google.com>
This changes the build workflow to first list all available `.po`
files, and then use this information to start parallel jobs which test
each translation.
* add ko.po
* translate ko(~23.01.19)
* change speaker-note ko
* change id
* translate ko(~23.01.20)
* ~day3 keynote
* draft done to f3446a91
* add @jiyongp comments of upstream PR #276.
* sync & apply review comments(upstream)
sync 585509bb
* After 10000 line apply review comments(upstream)
* chgange build.yml
* Fix the inconsistent newline character problem for the KO translation
If a msgid does not end with the newline character, so should the
msgstr.
Test: msgfmt --statistics -o /dev/null po/ko.po
No error, but shows `1085 translated messages, 675 untranslated
messages.`
---------
Co-authored-by: Evan kim(cli) <keispace.kyj@gmail.com>
