* da: Sync translation
This resulted in some rewrapped strings due to how `msgmerge` wraps
the strings compared to how `mdbook-xgettext` extracts them.
I also translated a few strings.
* Apply suggestions from code review
* zh-Hans: Translation for basic_syntax/references.md
* Add space between Chinese and English words
For better display effect when compiled to markdown file
Co-authored-by: wnghl <wnghilin@gmail.com>
---------
Co-authored-by: wnghl <wnghilin@gmail.com>
* Create zh-CN.po
Start the translation of Chinese (Simplified).
* Create zh-Hans.po
Start the translation of Chinese (Simplified).
* Delete zh-CN.po
Use zh-Hans instead of zh-CN unless there are translations for different regions.
This copies a bunch of untranslatable page titles (such as crate
names) to the translation. I also translated a lot of small and fuzzy
entries. We should now be at 200 translated entries.
* Additional Italian translations
* Updated base template
* git-ignoring backup copies `po/*.po~` files, generated when updating an existing translation
da: sync with c45b350
This is the result of running
MDBOOK_OUTPUT='{"xgettext": {"pot-file": "messages.pot"}}' mdbook build -d po
msgmerge --update po/da.po po/messages.pot
* First pass of automated translation, using https://github.com/mgeisler/cloud-translate
I think it can give this a leg start.
* First batch of corrections from automatic translations
The translation here comes from @wfranck, I merely resurrected it from #495.
* Translated Day 1: Morning
* Translated Day 1: Afternoon
---------
Co-authored-by: Walter Javier Franck <walterjfranck@gmail.com>
Co-authored-by: Kevin Islas <kevin.islas.abud@gmail.com>
Review of the translation for pt-BR.
Some terms cannot be translated.
Other terms have no translation and have been adapted.
Code examples have been translated, where possible, for ease of understanding.
* Update Korean Translation (20230217)
carg install & gen messages.pot & msgmerge
* Resolve fuzzy entries in Korean
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* Parse Markdown to support translation.
This upgrades from just splitting Markdown files on double-newlines, to
using a Markdown parser to break them into more appropriate chunks. The
upshot is that code samples are all in one message, lists are bundled
together, and generally it should be easier to translate.
* [WIP] helper to update po files for new translation
* process synthetic input file-by-file
* review comments
* remove temporary code
* fix msgfmt lints
* Update mdbook to 0.4.28
This version contains https://github.com/rust-lang/mdBook/pull/1986 which will allow us to test the code in each translation.
* Fix formatting in Korean translation
The extra code block made `mdbook test` fail.
* Update po/ko.po with the latest changes
```
$ MDBOOK_OUTPUT='{"xgettext": {"pot-file": "messages.pot"}}' mdbook build -d po
$ msgmerge --update po/ko.po --no-wrap po/messages.pot
```
* Resolve fuzzy translations in Korean
* Translate new texts into Korean
* Copy code blocks as msgstr in Korean
and fix some minor typos.
* Remove #~ lines from ko.po
* Address Jiyong's comments
* Fix typos and translate untranslated messages in Korean
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* Resolve fuzzy items in Korean
* Add missing translation in Korean (visibility)
* Translate filesystem in Korean
* Update po/ko.po
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Update po/ko.po
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Update po/ko.po
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* s/블럭/블록
* Add missing translation for Korean
* Fix spacing in Korean
along with typos.
* Add missing msgstr in Korean
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* Add missing translation in Korean
* Cosmetic refinement of Korean translation
* typo
* spacing
* newlines
* `_text_` into `*text*` or `*text*`
* removed a few "translation note"(역주)
* Fix typo in Korean
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* Run msgmerge --no-wrap --update po/ko.po po/messages.pot
* Be consistent with the line ending. For example, if the original text
ends with ":", so the translation is.
* Remove unnecessary newline characters
If a newline character is from the rendering of the source text, remove
it in the translated text.
* Fix the remaining inconsistencies on line ending chracters
* s/제너릭/제네릭/g
제네릭 seems to be the popular translation for "generic":
제너릭: 120K results
제네릭: 1M results
* s/트레이트/트레잇/g
트레잇 seems to be the popular translation for "trait" at least in the
Rust ecosystem. The Rust book also uses 트레잇.
https://rinthel.github.io/rust-lang-book-ko/appendix-08-glossary.html
* Revive the missing translations for the Translations section
* Resolve remaining fuzzy translations
* Update Korean translation
* Apply --no-wrap for Korean translation
Use `--no-wrap` for Korean translation to avoid unnecessary diffs.
When updating ko.po,
`msgmerge --no-wrap --update po/ko.po po/messages.pot`
Poedit's settings:
- uncheck "line-wrapping"
- uncheck "keep old formatting"
Note that with these settings/options `msgstr` will be still
line-wrapped at `\n`.
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* Remove all fuzzy items in Korean translation
* Apply grammar fixes in Korean Translation
of #440, #441
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* More polishing on the pt-BR translation
* Fix translation to make code compile
This was tested with `mdbook test` from
https://github.com/rust-lang/mdBook/pull/1986.
---------
Co-authored-by: Martin Geisler <mgeisler@google.com>
* Update Korean translation with latest English
- mdbuild build
- msgmerge --update
- poedit
* Resolve some fuzzy marks
and also add Korean translation for translations.md.
---------
Co-authored-by: Jooyung Han <jooyung@google.com>
* 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>
