I tried to translate the table of contents into Vietnamese.
- Some keywords are hard to translate, or to clarify my translation, I
used parentheses "( )".
- I don't know if I should keep some keywords in English or not. In this
pr I chose to translate them into Vietnamese and keep their original
English counterparts in parentheses.
- I could mention some of them like: build, type inference, trait, move
semantics, iterator, panic, unsafe...
- Some parts overlap with this pr:
https://github.com/google/comprehensive-rust/pull/1947
---------
Co-authored-by: Martin Geisler <martin@geisler.net>
I think the msg in the file maybe out of sync with
https://google.github.io/comprehensive-rust/control-flow-basics/exercise.html.
Should I continue to refer to the .po file as a source-of-truth, or
should I update the English message, as well as the Vietnamese
translation in this file?
Or should we re-sync the vi.po file first?
Here is the translation of *Day 1 Morning: Type and Values* translation.
It seems like there is no corresponding definition of *hygienic macros*
in Vietnamese, so I think keeping its English word is fine.
---------
Co-authored-by: Martin Geisler <mgeisler@google.com>
The English contents has changed, leading to untranslated session
outline and schedule because the msgid no longer match the original
contents. Additionally, incorrect file names are listed in the comment.
This PR follow the steps outlined in [Refreshing an Existing
Translation](https://github.com/google/comprehensive-rust/blob/main/TRANSLATIONS.md#refreshing-an-existing-translation)
to refresh the Vietnamese translation file. After the update, some
translated session outlines were no longer appropriated, so this PR also
updates all of them
The translation of *Welcome to Comprehensive Rust:
(1) Running the Course*.
I have followed the [Contributing
Guidelines](b38d429e49/CONTRIBUTING.md):
- [x] Edited by Poedit
- [x] Formatted by `dprint fmt`
- [x] Submitted to the CLA
