comprehensive-rust
comprehensive-rust copied to clipboard
google
Chinese (Simplified) translation
Hi Martin @mgeisler ! I've had a conversation with you via email about this translation a week ago. I'm working on this issue rn.
Edit by @mgeisler: See https://github.com/google/comprehensive-rust/issues/324#issuecomment-1562626220 below for instructions.
Hey @mgeisler: I saw that there's a machine-translated version by running the i18n script, could you run the script for the zh_CN locale for us?
(I think Hilbert had a similar script but we noticed some off-by-one errors..., so just wanted to see if these errors are specific to zh_CN locale.)
Thanks!
Hi @kiwiwarmnfuzzy, the script it here: https://github.com/google/comprehensive-rust/pull/291. I asked the other translators, and they tell me that they haven't seen the same off-by-one errors.
Here is the output from a fresh run of that script: zh_CN.zip.
Hi @kiwiwarmnfuzzy, the script it here: #291. I asked the other translators, and they tell me that they haven't seen the same off-by-one errors.
Here is the output from a fresh run of that script: zh_CN.zip.
Oh no worries I wasn't using your script. And thanks this output looks good - we can start from here.
Hi there, just a small note: please rename the file to zh-CN.po so that the translation will eventually appear under .../zh-CN/. The _ to - change should give us the right kind of language tag and this is the style we used for the Brazilian Portuguese translation in #381.
From reading https://developers.google.com/search/docs/specialty/international/localized-versions, I'm thinking we should name the Simplified Chinese translation zh-Hans like @taotieren does in #436.
From reading https://developers.google.com/search/docs/specialty/international/localized-versions, I'm thinking we should name the Simplified Chinese translation
zh-Hanslike @taotieren does in #436.
Got it. I've been occupied by my COVID and ISCA rebuttal lately. Will work on this from the coming week.
Got it. I've been occupied by my COVID and ISCA rebuttal lately.
Ugh, sorry to hear that! I had COVID myself last year and it was not fun at all... Good luck with the conference! :slightly_smiling_face:
Got it. I've been occupied by my COVID and ISCA rebuttal lately.
Ugh, sorry to hear that! I had COVID myself last year and it was not fun at all... Good luck with the conference! slightly_smiling_face
Thanks for the kind words :)
I think called Chinese Simplified is better. Can you post the WIP repo URL in this issuse?
@xusiwei Thanks for reaching out!
I think called Chinese Simplified is better.
Could you explain a little why 'Chinese Simplified' is better? Is the difference between Mandarin v.s. Simplified about speaking v.s. writing? (I'm not very experienced in internationalization and various terminologies, so I'm mildly curious.)
Can you post the WIP repo URL in this issuse?
#325 is the latest PR that I'm aware of. This Google Doc has all the pointers.
I think called Chinese Simplified is better.
Hi @xusiwei, I tried looking this up and from what I can understand, you're right: we should call the translation "Chinese (Simplified)" since we're referring to the script. Google Translate uses "Chinese (Simplified)" so that's why I'm suggesting this variation.
To everybody here (@est7, @xusiwei, @kiwiwarmnfuzzy, ...): could someone generate a nearly-empty po/zh-Hans.po file to get the translation kicked off? We've done that recently for #653 and #652 :smile:
It would be awesome to get this started so that people can have an easier time contributing follow-up translations.
Hi @mgeisler, just saw your email and I think this is very exciting! I was going to go through the course anyway so I'd love to help with at least some parts of this translation.
Hi @mgeisler, just saw your email and I think this is very exciting! I was going to go through the course anyway so I'd love to help with at least some parts of this translation.
Hey @markx, that's excellent! Please start by putting up a PR to create the PO file, see our translation instructions for how to do this.
Hi @mgeisler, I saw your email too. I can also help with the translation!
Hi @mgeisler I would like to help. How many people are needed for the Chinese translation? I was wondering how to avoid duplicate work?
To create the po file for Chinese, should we use zh-HANS or zh-CN for simplified Chinese? To give some context, see discussion here for Chinese variants. To me, maybe zh-CN makes more sense here, if we really want to consider the differences of usage at different regions.
Hi @mgeisler, I'm Doris. I'd like to help! How should I coordinate with other volunteers?
Hi @mgeisler, I'm Luke and I saw your email. I'd like to help with the translations! How should I participate in this?
To create the po file for Chinese, should we use zh-HANS or zh-CN for simplified Chinese? To give some context, see discussion here for Chinese variants.
Thanks for the link — I've also been trying to read up on this!
As written above and in your link, zh-Hans and zh-Hant are the recommended region neutral ways of denoting the Chinese written in einer simplified or traditional script. That's my current understanding and it matches how Google Translate has just two options
- Chinese (Simplified)
- Chinese (Traditional)
To me, maybe zh-CN makes more sense here, if we really want to consider the differences of usage at different regions.
This is something I cannot judge. My guy feeling would be to start with simplified and traditional translations — but that's just because I can see the difference even if I cannot read the scripts 🙂
Do you think the Rust community is large enough to have regional differences show up so that we should have CN, TW HK and SG translations?
Wow, thank you so much for the many positive replies! You're all amazing! :relaxed:
Many have asked me (via emails or via chat) what the next steps will be. I propose the following:
- First, we get the
zh-CN.pofile commited via #676 (@jzpin is on that). - After that, use this spreadsheet to coordinate.
- I've added everybody who expressed interest above — please add yourself!
- 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!
If there are people here who actually wanted to work on a Chinese (Traditional) translation, then please see the newly created #684!
I only have experiences on zh-CN and zh-TW. Translation between zh-CN and zh-TW is nontrivial. For example, the word software is translated to zh-CN as 软件 and the direct translation from simplified Chinese to the traditional Chinese is 軟件. But the correct translation is 軟體. Both 軟件 and 軟體 are in traditional Chinese. I am not sure if there are such differences in other regions like HK or SG.
Given all that, I agree to use zh-Hans and zh-Hant in this case, as we are most likely to have only two translations in the end. I just want to remind other participants to be aware of the issue.
Hi, I saw your post in misc-pek, glad to help with translation, added myself in the spreadsheet. :smiley:
