Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Traditional Chinese Translation Progress #1

Open
tesseralis opened this issue Feb 8, 2019 · 79 comments

Comments

@tesseralis
Copy link
Member

commented Feb 8, 2019

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:

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.

Basics

API Reference

Navigation

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

Next Steps

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

Installation

Hooks

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

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

Advanced Guides

  • Accessibility
  • Code-Splitting (@neighborhood999) #55
  • Context
  • Error Boundaries
  • Forwarding Refs
  • Fragments (@RickyWooo) #94
  • Higher-Order Components (@yikkok-yong)
  • Integrating with Other Libraries
  • JSX In Depth
  • Optimizing Performance (@chloewlin)
  • Portals
  • React Without ES6
  • React Without JSX
  • Reconciliation (@HcwXd) #95
  • Refs and the DOM
  • Render Props
  • Static Type Checking
  • Strict Mode
  • Typechecking With PropTypes
  • Uncontrolled Components
  • Web Components

FAQ

  • APIs and AJAX (@JuanitoFatas) #3
  • Babel, JSX, and Build Steps
  • Passing Functions to Components
  • Component State
  • Styling and CSS
  • File Structure
  • Versioning Policy
  • Virtual DOM and Internals

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

This comment has been minimized.

Copy link
Contributor

commented Feb 9, 2019

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

This comment has been minimized.

Copy link
Member Author

commented Feb 9, 2019

@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

This comment has been minimized.

Copy link
Member Author

commented Feb 9, 2019

@itszero I gave you the home page!

@chloewlin

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2019

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

@chloewlin

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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

@JuanitoFatas

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2019

I could take the Basics section and FAQs 🙋

@chloewlin

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2019

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.

@chloewlin

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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

@itszero

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2019

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!

@haimengzhang

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

@itszero

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2019

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.

@chloewlin

This comment has been minimized.

Copy link
Member

commented Feb 10, 2019

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.

@haimengzhang

This comment has been minimized.

Copy link
Member

commented Feb 11, 2019

@chloewlin

This comment has been minimized.

Copy link
Member

commented Feb 12, 2019

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

@itszero

This comment has been minimized.

Copy link
Contributor

commented Feb 12, 2019

I'll also take another one: Introducing JSX.

@neighborhood999

This comment has been minimized.

Copy link
Member

commented Feb 12, 2019

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

By the way, I take the Rendering Elements.

@ivan-ha

This comment has been minimized.

Copy link
Contributor

commented Feb 16, 2019

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

Maybe I could take Conditional Rendering?

@chentsulin

This comment has been minimized.

Copy link
Member

commented Feb 17, 2019

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

@chloewlin

This comment has been minimized.

Copy link
Member

commented Feb 17, 2019

@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. :)

@haimengzhang

This comment has been minimized.

Copy link
Member

commented Feb 18, 2019

I'll claim Handling Events if no one is.

@chloewlin

This comment has been minimized.

Copy link
Member

commented Mar 22, 2019

@vrabe @fabianlee1211 @barrypeng6 welcome! Please (1) read some of the translations we have merged in and (2) check out glossary in wiki that the community has agreed to keep in English. (3) Open a PR once you have started your translation. Find me on Twitter if you have any questions!

@piovischioh

This comment has been minimized.

Copy link
Contributor

commented Mar 25, 2019

I could take Using the State Hook for the next.  

@barrypeng6

This comment has been minimized.

Copy link
Contributor

commented Mar 25, 2019

Hi, @chloewlin I also take Test Renderer. Thx.

@chloewlin

This comment has been minimized.

Copy link
Member

commented Mar 25, 2019

@piovischioh @barrypeng6 no problem! The top list has been updated.

@BruceWeng

This comment has been minimized.

Copy link
Contributor

commented Mar 25, 2019

@chloewlin Hooks at a Glance was merged.
I will take Using the Effect Hook next. Please help me to update the list for ownership. Thanks!

@bugtender

This comment has been minimized.

Copy link
Member

commented Mar 25, 2019

@BruceWeng No problem, I updated it. 👍

@fabianlee1211

This comment has been minimized.

Copy link
Contributor

commented Mar 28, 2019

@chloewlin I would like to move on to Add React to a Website please!

@neighborhood999

This comment has been minimized.

Copy link
Member

commented Mar 28, 2019

Hi @fabianlee1211, No problem! I updated the list.

@chloewlin

This comment has been minimized.

Copy link
Member

commented Mar 31, 2019

I'll claim Handling Events if no one is.

Hey @haimengzhang how are you doing on this translation? If you are too busy to do it, let me know so that I can take over.

@fabianlee1211

This comment has been minimized.

Copy link
Contributor

commented Apr 2, 2019

@chloewlin it's me again I'll take the remaining parts for Installation if that's ok.

@neighborhood999

This comment has been minimized.

Copy link
Member

commented Apr 13, 2019

@fabianlee1211 I updated the list, thank you.

@dolphinlin

This comment has been minimized.

Copy link

commented Apr 16, 2019

In my opinion, UI is more clear and better than 使用者介面.

@chloewlin

This comment has been minimized.

Copy link
Member

commented May 25, 2019

Hey @haimengzhang, it's been a while since we hear from you last time. I am going to translate Handling Events so that we can complete the Basics section this weekend. Sorry! Please feel free to work on other translations when you have time. 🙂

@KevinHu2014

This comment has been minimized.

Copy link
Contributor

commented Jun 2, 2019

Hi @chloewlin
Can I take Rules of Hooks please?

@chloewlin

This comment has been minimized.

Copy link
Member

commented Jun 3, 2019

Hi @KevinHu2014, yes, I've assigned it to you. Please read the community guidelines and open a PR for it. Welcome!

@ivan-ha

This comment has been minimized.

Copy link
Contributor

commented Jun 6, 2019

@chloewlin me again, would like to take Hooks API Reference 🙋‍♂

@chloewlin

This comment has been minimized.

Copy link
Member

commented Jun 8, 2019

hey @ivan-ha good to see you again! Here you go. Looking forward to seeing your PR.

@neighborhood999

This comment has been minimized.

Copy link
Member

commented Jun 26, 2019

I take the Building Your Own Hooks and Hooks FAQ.

@chloewlin

This comment has been minimized.

Copy link
Member

commented Jun 30, 2019

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.

@BruceWeng

This comment has been minimized.

Copy link
Contributor

commented Jul 2, 2019

@chloewlin I might not have time working on Using the Effect Hook recently. Free to release it to the community!

@leah-z-liu

This comment has been minimized.

Copy link

commented Jul 4, 2019

Hey @chloewlin I'd love to help! Can I take Using the Effect Hook?

@chloewlin

This comment has been minimized.

Copy link
Member

commented Jul 4, 2019

Hey @leah-z-liu, yes, you can take it if you are comfortable translating in Traditional Chinese. Please take a look at our wiki and the already translated Hook articles for reference. Welcome. :)

@chloewlin

This comment has been minimized.

Copy link
Member

commented Jul 5, 2019

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)

  • ReactDOMServer
  • SyntheticEvent
@RickyWooo

This comment has been minimized.

Copy link
Contributor

commented Sep 5, 2019

Hi @chloewlin , looks like both ReactDOMServer & SyntheticEvent chapter have been translated, may I take Fragments and make a little contribution? thanks :)

@chloewlin

This comment has been minimized.

Copy link
Member

commented Sep 5, 2019

@RickyWooo of course! I put your name down already.

@chloewlin

This comment has been minimized.

Copy link
Member

commented Oct 7, 2019

Hi @leah-z-liu! Have you finished your work on the Effect Hook? :) The community is really looking forward to completing the translation regarding Hooks soon. Let me know where you're at.

@yikkok-yong

This comment has been minimized.

Copy link

commented Oct 10, 2019

Hi @chloewlin, I would like to contribute translating the Higher Order Component.

@leah-z-liu

This comment has been minimized.

Copy link

commented Oct 10, 2019

Hi @leah-z-liu! Have you finished your work on the Effect Hook? :) The community is really looking forward to completing the translation regarding Hooks soon. Let me know where you're at.

Hey @chloewlin the translation is about 80% done. I'll submit PR this weekend :)

@chloewlin

This comment has been minimized.

Copy link
Member

commented Oct 10, 2019

Hi @yikkok-yong, welcome! It's yours. Hey @leah-z-liu, thanks for your update. I look forward to reviewing it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.