Chinese (Traditional) translation

[mgeisler]

Discuss a Chinese (Traditional) translation (zh-TW) of the course. For reference, here is a translation of the Rust Book: https://github.com/rust-tw/book-tw.

For the Chinese (Simplified) translation, please see #324.

[mgeisler]

Just like for Chinese (Simplified), I suggest coordinating the work on this translation via a spreadsheet.

1. First, we need someone to put up a PR to get a zh-Hant.po file committed
2. After that, use this spreadsheet to coordinate.
   • Please add yourself on the first page!
   • Pick a file from the second sheet and add your Github username next to it to claim it.
     • Change the state to "In progress" and
     • Add today's date to the last change column.
   • The spreadsheet is editable by everybody (both inside and outside of Google) so you can add/remove things, comment on it and generally update it to suit your needs.

Please send small PRs! I suggest translating the titles in the SUMMARY.md file as you translate the content itself, but that will naturally lead to contention on that file. Perhaps you want to instead agree upfront about the wording for the titles? Our discussions would be a good place to do this.

See #683 for a just-started discussion about where to coordinate a translation table. You might want to create a similar table — in the spreadsheet, in the PO file directly, or in a discussion post.

Let me know if I've forgotten something or can help in any other way!

[mgeisler]

Hi all, we need someone to put up an empty (or nearly empty) po/zh-Hant.po file using the translation instructions.

Please let me know if you run into any trouble with this!

[mgeisler]

Hi all, we need someone to put up an empty (or nearly empty) po/zh-Hant.po file using the translation instructions.

Please let me know if you run into any trouble with this!

I went ahead and created #697 for this since I already have everything setup locally.

[hueich]

Thanks for getting this started!

[mgeisler]

Thanks for getting this started!

Thanks for the review on #697! You have an eye for detail and I invite you to add yourself to CODEOWNERS if you're interested in reviewing more changes :smile:

[hueich]

Sent https://github.com/google/comprehensive-rust/pull/702

[edong]

Hello fellow contributors, I've added a tab to the spreadsheet to take a first stab at coming up with a terminology list with translations.

I think it often makes sense to include the English term in parentheses when first using a Chinese term.

[mgeisler]

Hi all,

I've talked more with people at Google about the naming of the translation and it turns out I was wrong in recommending zh-Hant here. The vocabulary is different between Taiwan and Hong Kong, even though they both use Traditional Chinese script.

So I will like us to rename the po/zh-Hant.po file to po/zh-TW.po. @edong, you were the one who made me aware of the differences... would you be up for sending a PR to rename the file?

Also, I recently added a list of incomplete translations. Let me know when you want to mention the translation there — I would suggest doing so after translating the first few pages.

[mingyc]

Sent out https://github.com/google/comprehensive-rust/pull/757 to rename zh-Hant.po to zh-TW.po

[mgeisler]

Hey all, I've sent more chapters to our localization team and will be putting up more PRs soon. Thanks for all the help in reviewing this!

[mgeisler]

Hi all! It would be great if someone could refresh the translation with msgmerge after installing the new version of mdbook-i18n-helpers. After the normalization in #1100, you need a refresh to get new strings incorporated and to mark old strings as obsolete.

[mgeisler]

Hi all! Thanks to #1218, the Traditional Chinese translation is now being published automatically on every merge to main. See: https://google.github.io/comprehensive-rust/zh-TW/.

What you see there is the result of translating the current English strings — if your PO file is not up-to-date, the course reverts to English (see https://github.com/google/mdbook-i18n-helpers/issues/16 for ideas on how to improve this). This is why running msgmerge every 2-3 weeks is so important.

@henrif75 is working with our Localization team to translate the missing content and I hope it will be ready for review in a few weeks.

[mgeisler]

Hey folks, just a heads up that we're tinkering with publishing the course as a PDF — including for the translations: #1572.

If you have input on the font to use, please let us know!

[henrif75]

The untranslated content from v2 was sent to the translation service.

[henrif75]

I'm going to merge the content that was already been translated to v.2 (Day 1 until Android) and start helping users, while we're waiting for the Bare Metal and Concurrency sections.