Jiyong Park

I wish we have a few more rounds before we publish it. I haven't finished proof-reading and revising it. See #302 for my progress.

That's fair. Then let me finish proof-reading and revising the content for first day at least. Then we can publish for broader contribution.

Thanks, @keispace again. As a follow-up, I've created #302 (draft) to further revise the translation.

Current status: day 1, day 2, day 3 morning, and day 4 were merged. day 3 afternoon under review (#422).

Thanks. That will work. Besides, I started updating the Korean translation this week. The progress is (and will be) slow, but just wanted to let you know.

> 안녕하세요. 관심있는 분이 또 계시니 반갑네요. 저는 현재 전체 번역 초안이 완료 되고 1월 25일 기준으로 google/main 수정사항을 작업 중입니다. 아직 완료는 되지 않았지만 필요하시면 작업중인(fuzzy 부분 및 4일차...

No. I don't think we (Korean translators) have reached to a consensus on that. Even the Korean translation of the Rust book is inconsistent in its translations of comments. I...

> * Copying and Cloning: I don't think we need to use the original language as it is, as it can be divided into 복사 and 복제 rather than copying...

@keispace, please fix the errors from `Test/translations (ko)`. There are multiple places where the newline character is missing. Or you may follow the instructions at https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork (which is basically selecting...

I've merged #300 which is an amendment of this PR. Let's close this here. Thanks @keispace for your contribution.