[OLD] Legacy Traditional Chinese Translation Progress

[tesseralis]

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate.
3. Clone this repo, translate your page, and submit a pull request!

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.

For maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

• Home Page (@tesseralis) [OLD] Legacy Traditional Chinese Translation Progress #1

When PRs are merged, make sure to mark that page as completed!

Core Pages

To do before releasing as an "official" translation. Please translate these pages first.

• Home Page (@itszero) [Homepage] initial translation #6
• Tutorial (@chloewlin) Tutorial #9

Basics

• Hello World (@JuanitoFatas) docs(zh-hant): Translate Hello World #4
• Introducing JSX (@itszero) docs(zh-hant): introducing jsx #13
• Rendering Elements (@neighborhood999) docs(tw): translate rendering elements #11
• Components and Props (@bugtender) docs(zh-hant): Translate Components and Props #12
• State and Lifecycle (@neighborhood999) docs(tw): translate state-and-lifecycle #16
• Handling Events (@chloewlin) docs: Handling events #74
• Conditional Rendering (@ivan-ha) doc: translate conditional rendering #18
• Lists and Keys (@chloewlin) Complete lists-and-keys #17
• Forms (@chloewlin) New PR for form #59
• Lifting State Up (@neighborhood999) docs(tw): translate lifting-state-up #33
• Composition vs Inheritance (@neighborhood999) docs(tw): translanslate composition-vs-inheritance #39
• Thinking in React (@chloewlin) doc: complete think in react #20

API Reference

• React (@itszero) [api] react #28
• React.Component (@chloewlin) docs: React.Component #75
• ReactDOM (@abrcdf1023) doc: Translate ReactDOM #38
• ReactDOMServer (@chloewlin) docs: ReactDOMServer #80
• DOM Elements (@piovischioh) doc: translate dom-elements #40
• SyntheticEvent (@chloewlin) docs: synthetic-event branch #81
• Test Utilities (@vrabe) doc: Test Utilities #56
• Shallow Renderer (@barrypeng6) doc: translate shallow renderer #42
• Test Renderer (@barrypeng6) doc: translate Test Renderer #43
• JS Environment Requirements (@ivan-ha) docs: translate js environment requirement #37
• Glossary (@ivan-ha) docs: translate glossary #36

Navigation

These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.

• tutorial/nav.yml (@chloewlin) Set up tutorial branch #78
• docs/nav.yml (@neighborhood999) docs: translate nav.yml and some wording #70

Next Steps

These are the next most important translations, ordered by importance:

Installation

• Getting Started (@fabianlee1211) doc: Translate Getting Started #41
• Add React to a Website (@fabianlee1211) doc: translate add react to a website #45
• Create a New React App (@fabianlee1211) doc: translate create a new react app #52
• CDN Links (@fabianlee1211) doc: translate cdn links #50

Hooks

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

• Introducing Hooks (@chentsulin) doc: translate hooks-intro #34
• Hooks at a Glance (@BruceWeng) doc: translate hooks-overview #35
• Using the State Hook (@piovischioh) doc: translate hooks-state #67
• Using the Effect Hook (@leah-z-liu) docs: hooks-effect #103
• Rules of Hooks (@KevinHu2014) doc: translate hooks-rules #63
• Building Your Own Hooks (@neighborhood999) docs: translate hooks-custom #72
• Hooks API Reference (@ivan-ha) docs: translate hooks API reference #69
• Hooks FAQ (@neighborhood999) docs(hooks): translate hook faq #97

Warnings

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.

• dont-call-proptypes
• invalid-aria-prop
• invalid-hook-call-warning
• legacy-factories
• refs-must-have-owner
• special-props
• unknown-prop (@neighborhood999)

Advanced Guides

• Accessibility (@chloewlin) Accessibility #112
• Code-Splitting (@neighborhood999) docs(code-splitting): translate code splitting #55
• Context (@chloewlin)
• Error Boundaries (eyeccc) doc: translate error boundaries to zh-hant #104
• Forwarding Refs (eyeccc) Translate: Forwarding ref #118
• Fragments (@RickyWooo) docs: translated Fragments.md #94
• Higher-Order Components (@yikkok-yong)
• Integrating with Other Libraries
• JSX In Depth (@aboudicheng) docs: JSX in Depth #102
• Optimizing Performance (@chloewlin)
• Portals (@henry61024) docs(Advanced guides): Translate Portals #199
• Profiler (@henry61024)
• React Without ES6 (@henry61024) docs(Advanced guides): React without ES6 #203
• React Without JSX (@yunkii) Merge pull request #122 from yunkii/yunkii #122
• Reconciliation (@HcwXd) docs: Reconciliation #95
• Refs and the DOM (@eyeccc) translate refs and the dom #120
• Render Props (@huantingwei) docs: translate Render Props #176
• Static Type Checking (@vrabe)
• Strict Mode (@eyeccc) doc: translate strict mode to zh-hant #105
• Typechecking With PropTypes (@yunkii)
• Uncontrolled Components (@eyeccc) doc: translate uncontrolled components to zh-hant #106
• Web Components (@eyeccc) doc: translate web components to zh-hant #107

FAQ

• APIs and AJAX (@JuanitoFatas) docs(zh-hant): Translate FAQ: AJAX and APIs #3
• Babel, JSX, and Build Steps (@lithiumpie) docs(faq): translate faq-build #160
• Passing Functions to Components
• Component State (@lithiumpie) docs(faq): translate faq-state #162
• Styling and CSS (@huantingwei) docs: translate faq-styling #201
• File Structure (@huantingwei) docs: translate faq-structure #204
• Versioning Policy
• Virtual DOM and Internals

Testing

• Testing Overview (@neighborhood999) docs(testing): translate testing.md #148
• Testing Recipes
• Testing Environments (@neighborhood999) docs(testing): translate testing-environments #149

Contributing

Priority: Low

• How to Contribute
• Codebase Overview
• Implementation Notes
• Design Principles

Components

Components in src/components that have some text in them.

• CodeEditor
• CodeExample
• ErrorDecoder
• LayoutFooter
• LayoutHeader
• MarkdownPage

Additional Translations

These are not the primary translation targets.

• Blog
• Community

[itszero]

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! 😄

[tesseralis]

@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!

[tesseralis]

@itszero I gave you the home page!

[chloewlin]

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!

[itszero]

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

[chloewlin]

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!

[neighborhood999]

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.

[bugtender]

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.

[bugtender]

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

[JuanitoFatas]

I could take the Basics section and FAQs 🙋

[chloewlin]

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!

[JuanitoFatas]

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.