I'd love to help! Maybe I can try by taking the Home page first?

I'm slightly confused about the process though. Should we be working on Crowdin or work off this repo and submit a PR instead?

Thanks! 😄

@itszero you should work off this repo and submit a PR. You can copy-paste from crowdin if you find that a useful start to your translations!

@itszero I gave you the home page!

Hi @itszero, welcome to the team! 👍

There are currently five maintainers for this version. Some people are in Taiwan and are on vacation. We will also discuss how to coordinate with everyone else soon!

Got it. I also got your email, will discuss it further offline with you. Thanks for coordinating.

Hi @chentsulin, @neighborhood999, @bugtender, @itszero, and @haimengzhang, welcome to the team!

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:

1. Standardization of Glossary: I want to bring your attention to chentsu's complete Redux translation and a popular React handbook that have served the function of an official doc. Both translations are great! I suggest we use them as references to standardize technical glossary to ensure that all the technical terms are consistent across the entire documentation. Why? Two reasons: (1) Our translation will set up the standard for how people understand or talk about React in the Chinese speaking world, since there are no official docs for React yet. (2) Contributors and reviewers might have different opinions on how things should be translated. It will be more efficient to agree on these terms first.

   Examples of ambiguities we should discuss:

   • Should Component be 元件, 組件, 元素 ? Will there be collisions? (Definitely not 元素 in my opinion since it sounds more like an element.)
   • Should we keep render as render in English or translate it as 渲染 or 描繪 ? (See
     Simplified Chinese for reference) As @itszero pointed out, 渲染 is often used in 3D modeling. We could even consider keeping react-specific methods like render and componentDidMount as they are in English.

   For ambiguities like these, we can set up a quick one hour conference call to reach a consensus on the glossary before we head out to work on our part of the translation.

2. Standardization of Style: Most of open source contributors follow this Chinese copywriting guidelines. Nat created a universal guide. We should follow them.

3. Transparency of Discussion: To facilitate discussion between contributors and reviewers, we could consider communicating over Twitter or other platforms. But we should always keep github as the source of truth and keep our great @tesseralis updated with our progress.

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, Component can translate 元件 or 組件, but in some technical term like “Higher Order Component”, maybe we can translate to “高階元件（組件）”, but for the beginners they are maybe not familiar with this technical term, so I think to keep the original term can let beginners recognize common technical terms. In the most (English) article, people will see the “Higher Order Component” not the “高階元件（組件）”.

Maybe we can create a list of glossary for the Traditional Chinese, list common terms and describe the terms should be translated or not.

Hi, everyone.
I have read chentsu's Redux book when I learn Redux before. And I agree it's a good reference for us. As @neighborhood999 said, maybe we can create the first glossary base on the glossary from this book.

Oh, and I'll take the Tutorial's part. 😂 Happy Lunar New Year 🧨

I could take the Basics section and FAQs 🙋

Awesome. I want to quote how @chentsulin translates reducer:

reducer (也稱作 reducing function) 是一個 function，它接收累積值和一個值並回傳新的累積值。它們通常被用來把一組值 reduce down 成一個單一值。

Notice how he uses English for 'reducer', 'function', and even 'reduce down'.

Reducer 不是 Redux 獨有的—它們是 functional programming 裡的基礎概念。甚至大多數的非 functional language，像是 JavaScript，都有一個內建的 reducing API。在 JavaScript 裡，那就是 Array.prototype.reduce()。

Notice how 'functional programming' is in English.

在 Redux 裡，累積值就是 state 物件，而被累積的值就是 action。Reducer 依照先前的 state 和一個 action 來計算一個新的 state。它們必須是 pure function—就是對給定的 input 每次會回傳完全一樣的 output 的 function。它們也應該是沒有 side-effect 的。這就是使像是 hot reload 和 time travel 等令人興奮的功能成真的東西。

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!

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?

Sounds good to me.

We're deciding on translation style now, and will set up an initial conference call or a platform for everyone. Please join us!

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.

@itszero @neighborhood999 @chentsulin @bugtender @haimengzhang @JuanitoFatas Now that our team is growing, it is indeed getting harder to coordinate with everyone.

We can still set up Slack, Spectrum, Twitter, or Telegram. NO Line because @itszero doesn't have Line. Please voice your preference.

Nice to see everyone online now. 😄 If we'd like to keep the conversation more open and accessible: Spectrum is a good idea. Otherwise, I'm on all the other three platforms (preference wise: Telegram > Twitter > Slack).

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!

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 组件 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.

I updated the list from the top. I will work on translating the tutorial.

I'll also take another one: Introducing JSX.

@itszero I update the list on the above, assign Introducing JSX for you, thank you.

By the way, I take the Rendering Elements.

Hello there! React dev from Hong Kong and love to help!

Maybe I could take Conditional Rendering?

I will take Hooks part if no one works on it.

@ivan-ha I will update your name on conditional rendering. Remember to read the glossary page in Wiki and follow the style guide. Welcome.

@chentsulin No problem! I am also interested in that, but I am still working on tutorials now. Let me know if you need extra help. :)

I'll claim Handling Events if no one is.

I am taking Accessibility (#112) and Context in Advanced Guides.

Hey @chloewlin
I'll take Forwarding Refs (#118).
Thanks

Hi @eyeccc, thank you for helping!

I updated the list.

hi @chloewlin
i'll take one more translation: Refs and the DOM (#120) :)

@eyeccc thanks for tagging me! I updated the list for you. It's Christmas here so I've been a little slow in response. I look forward to your PR. :)

Hi @neighborhood999 , @chloewlin
I'm taking the React without jsx. (#122) and Typechecking With PropTypes

Hi @yunkii, thank you for helping! I'm updated the list for you.

I will take Testing Overview.

I'll take Testing Environments.

@neighborhood999 hi, I'm going to take faq-build

@lithiumpie Thank you for your help!

Hey~ @neighborhood999 I take faq-state

Hey~ @neighborhood999 I take faq-state

I updated list, thank you for help!

Hi, I wonder if the translation is still in progress?
If so, I would like to take Render Props under Advanced Guides. Thanks!

Hey @huantingwei yes it is! I'll add your handle to the list. Go for it. Feel free to ping me or @neighborhood999 for PR reviews.

Hello, I want to take Static Type Checking.

Hi @vrabe, it's yours! As always, please open a PR so that we can track your progress and review your contribution at the end. Let me know if you have any questions.

Hi, I'd like to translate the article: Portal. Is it still available?

Hi, @henry61024 yes! Thanks for helping. I'll update the list. 👍

Hello, may I take FAQ: File Structure and FAQ: Styling and CSS?

@huantingwei yes, and welcome! I will update the list. Please feel free to ping me, @bugtender or @neighborhood999 for reviews :)

Hi, I would like to work on React Without ES6 and Profiler translation too, but it seems that Profiler is not on the list. Is it still available?

@henry61024 Thanks for helping. You're right, seems Profiler missing, I also update the list and assign React Without ES6 and Profiler for you.

I take the unknown-prop.

I take the Virtual DOM and Internals

Thanks to everyone who contributed to the old website translation!
I've updated the issue for the new website: #260