* pt-BR.po: fine tuning for slide #1
* pt-BR.po: orador -> instrutor
Orador is a person who speaks to the public while instrutor is literally a trainer.
* 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.
* Refine ko-translation for "15.methods"
* Fix typo in ko (src/enums/variant-payloads.md:35)
* Refine ko-translation for Day 2
* Fix syntax errors
* Fix newlines
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
I started using poedit to work on the translation, which has
reformatted large parts of the file, so the change is a lot larger
than just the newly translated parts.
* 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.
* 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>
* 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
* 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>
