* zh-TW: translate structs
Part of #684.
* zh-TW: Apply suggestion to speaker notes about newtypes.
* zh-TW: Apply suggestion to speaker notes about newtypes.
---------
Co-authored-by: Jonathan Hao <phao@google.com>
* Remove statement that data is moved when assigning
The distinction between non-`Copy` and `Copy` types is tricky to explain. One problem is that people often focus on _moving_ vs _copying_ when both variable types always copy data.
This PR removes the statement about moving data (since that is wrong on its own).
* Apply suggestions from code review
Co-authored-by: Dustin J. Mitchell <djmitche@google.com>
* Apply suggestions from code review
Co-authored-by: Dustin J. Mitchell <djmitche@google.com>
---------
Co-authored-by: Dustin J. Mitchell <djmitche@google.com>
* ko: refresh translation for async
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: move translations back to where they belong
Moving them back helps avoid conflicts. The outdated messages can be
cleaned up with `msgmerge` at a later point.
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for error-handling
Part of #925.
* ko: move translations back to where they belong
Moving them back helps avoid conflicts. The outdated messages can be
cleaned up with `msgmerge` at a later point.
* Rust isn't functional, but it does have functional elements
* End sentence
Co-authored-by: Martin Geisler <martin@geisler.net>
* add info about OO
---------
Co-authored-by: Martin Geisler <martin@geisler.net>
* ko: refresh translation for concurrency
Part of #925.
* ko: move translation back to where it belongs
This is likely outdated, but moving it here helps avoid conflicts. The
outdated paragraph can be cleaned up with `msgmerge` at a later point.
* ko: refresh translation for android
Part of #925.
* ko: move translations back to where they belong
Moving them back helps avoid conflicts. The outdated paragraphs can be
cleaned up with `msgmerge` at a later point.
* ko: refresh translation for pattern-matching
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: move translation back to where it belongs
This is likely outdated, but moving it here helps avoid conflicts. The
outdated paragraph can be cleaned up with `msgmerge` at a later point.
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for generics
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: move translation back to where it belongs
This paragraph is likely outdated, but moving it here helps avoid
conflicts. The outdated paragraph can be cleaned up with `msgmerge` at
a later point.
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Added steps to configure Poedit properly
* Small adjustments
* Add link to Poedit
* Fix file formatting
* One. More. dprint. Fix.
* Normalizes pt-BR.po file format through Poedit
with line wrap.
* Fix typo.
* Fix fuzzy entries after .po file reformatting.
* Fix one code sample
* Added steps to configure Poedit properly
* Small adjustments
* Add link to Poedit
* Fix file formatting
* One. More. dprint. Fix.
* Normalizes pt-BR.po file format through Poedit
with line wrap.
* Fix typo.
* ko: refresh translation for modules
Part of #925.
* Apply suggestions from code review
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>
