Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Traditional Chinese Translation Progress #1
For New Translators
To translate a page:
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find find that you can't commit any more, let the maintainers know so they can assign the page to someone else.
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
To do before releasing as an "official" translation. Please translate these pages first.
These are the navigation links that appears in the sidebar. Possibly wait until
These are the next most important translations, ordered by importance:
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.
These are not the primary translation targets.
I know half of you are still on vacation, but it's about time for us to get started! @itszero is already working on homepage. Everyone, please look at the content and claim what you'd like to work on. :)
A few thoughts:
Feel free to provide other sample translations we can use as references. Any thoughts on how we can improve the process are much appreciated. Again, welcome to the team!
I prefer to keep some tech terms as the original. As @chloewlin mentioned above:
In the Traditional Chinese,
Maybe we can create a list of glossary for the Traditional Chinese, list common terms and describe the terms should be translated or not.
Awesome. I want to quote how @chentsulin translates reducer:
Notice how he uses English for 'reducer', 'function', and even 'reduce down'.
Notice how 'functional programming' is in English.
Notice how 'pure function', 'input', 'output', and even 'side-effect' are all in English.
Given that we all code in English, sometimes it's better to mix English with Chinese, rather than coming up with awkward translations that no one really uses. Can we all agree on this?
@JuanitoFatas welcome to the team! We're deciding on translation style now, and will set up an initial conference call or a platform for everyone. Please join us!
Sounds good to me.
Could we try a way (issue or wiki) to discuss these terms that in asynchronous fashion? People have different time and priorities, may be hard to schedule a meeting time that works for all of us.
Nice to see everyone online now.
Totally agree on keeping some words in English -- as for the extent, we can discuss that later. I think the last example in @chloewlin's reply feels a bit too fragmented.
I'll try to give the home page a first-pass tomorrow. Looking forward to work with y'all!
Hi everyone, Nice to work with you all. With communication channels, I'd prefer Slack or Twitter, but I will go with what most people prefer. Just a note, I'm also translating in Simplified Chinese at the mean time, and "component" is tranlated to 组件, shall we keep it consistent? In general, do we want to keep the vocabs consistent with the Simplified Chinese team? Haimeng…
On Sun, Feb 10, 2019, 4:56 AM Zero Cho ***@***.*** wrote: Nice to see everyone online now.
Personal Opinion I think the target audience of having Traditional Chinese translation is mostly for Taiwanese users. Therefore, we should strive for localizing it for those users too. I don't think people will cross-reference SC/TC documents so keeping that consistent doesn't make much more sense than making it easier to read to our target audience. We also briefly chatted about the possibility of keeping more terms in its English form above.
Hey @haimengzhang! So I agree with @itszero. Personally, the reason why I want to work on Traditional Chinese is because I find it very difficult to understand the way React is translated in Simplified Chinese. I would not use
Ok, sounds good to me! :)…
On Sun, Feb 10, 2019, 5:55 PM Chloe Lin ***@***.*** wrote: Hey @haimengzhang <https://github.com/haimengzhang>! So I agree with @itszero <https://github.com/itszero>. Personally, the reason why I want to work on Traditional Chinese is because I find it very difficult to understand the way React is translated in Simplified Chinese. I would not use 组件 or 渲染 because that is not how people who don't use Simplified Chinese would use. It would be pointless to keep them consistent since they are by nature two very distinct languages with different vocabulary and syntax. In other words, we're no just changing characters. We want to create high-quality, natural, accurate translations for readers in Traditional Chinese. And FYI, 组件 sounds like lego to me. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATTNC4ARGnS22Fvco_uiOdJ-iIkAZZSjks5vMLFvgaJpZM4atrCC> .
Hey everyone, we only have 26% left to be done. For those who have claimed some articles but haven't set up a PR, can you confirm that you are still interested/available to finish your translation?
Also, if you don't have time to finish what you are working on, you can still push your draft up and let someone else pick it up. If your article is too long, feel free to split up sections and let me help you.
Hey @abrcdf1023 and @dennisgl, I haven't heard back from y'all for a while, so I had to update the list so that others can take them over. If you're still interested in helping, please ping me or contribute to other articles in this list. :)
For other contributors: if you can, prioritize a core page. Let's meet the 100% core page first before we charge ahead! There are only two left: (I am working on the very long react component page now but can take either one afterwards)