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.

Sign up for GitHub

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

Jump to bottom

[OLD] Legacy Traditional Chinese Translation Progress #1

Closed
61 of 92 tasks
tesseralis opened this issue Feb 8, 2019 · 110 comments
Closed
61 of 92 tasks

[OLD] Legacy Traditional Chinese Translation Progress #1

tesseralis opened this issue Feb 8, 2019 · 110 comments
Assignees
@chloewlin

Comments

@tesseralis
Copy link
Member

tesseralis commented Feb 8, 2019 •
edited by neighborhood999
Loading

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 (@neighborhood999)

Advanced Guides

FAQ

Testing

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
Copy link
Contributor

itszero 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
Copy link
Member Author

@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
Copy link
Member Author

@itszero I gave you the home page!

@chloewlin
Copy link
Member

chloewlin commented Feb 10, 2019 •
edited
Loading

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
Copy link
Contributor

itszero commented Feb 10, 2019

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

@chloewlin
Copy link
Member

chloewlin commented Feb 10, 2019 •
edited
Loading

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
Copy link
Member

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.

@JuanitoFatas JuanitoFatas mentioned this issue Feb 10, 2019
Merged
@bugtender
Copy link
Member

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
Copy link
Member

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

@JuanitoFatas JuanitoFatas mentioned this issue Feb 10, 2019
Merged
@JuanitoFatas
Copy link
Contributor

JuanitoFatas commented Feb 10, 2019 •
edited
Loading

I could take the Basics section and FAQs 🙋

@chloewlin
Copy link
Member

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
Copy link
Contributor

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
Copy link
Member

chloewlin commented Feb 10, 2019 •
edited
Loading

@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
Copy link
Contributor

itszero 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
Copy link
Member

haimengzhang commented Feb 10, 2019 via email

@itszero
Copy link
Contributor

itszero 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
Copy link
Member

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
Copy link
Member

haimengzhang commented Feb 11, 2019 via email

@chloewlin
Copy link
Member

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

@itszero
Copy link
Contributor

itszero commented Feb 12, 2019

I'll also take another one: Introducing JSX.

@neighborhood999
Copy link
Member

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

By the way, I take the Rendering Elements.

@bugtender bugtender mentioned this issue Feb 13, 2019
Merged
@bugtender bugtender pinned this issue Feb 14, 2019
@ivan-ha
Copy link
Contributor

ivan-ha commented Feb 16, 2019 •
edited
Loading

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

Maybe I could take Conditional Rendering?

@chentsulin
Copy link
Member

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

@chloewlin
Copy link
Member

@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
Copy link
Member

I'll claim Handling Events if no one is.

@chloewlin
Copy link
Member

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

@eyeccc
Copy link
Contributor

eyeccc commented Dec 20, 2019

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

@neighborhood999
Copy link
Member

Hi @eyeccc, thank you for helping!

I updated the list.

@eyeccc
Copy link
Contributor

eyeccc commented Dec 26, 2019

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

@chloewlin
Copy link
Member

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

@yunkii
Copy link
Contributor

yunkii commented Dec 29, 2019 •
edited
Loading

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

@neighborhood999
Copy link
Member

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

@neighborhood999
Copy link
Member

I will take Testing Overview.

@neighborhood999
Copy link
Member

I'll take Testing Environments.

@lithiumpie
Copy link
Contributor

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

@neighborhood999
Copy link
Member

@lithiumpie Thank you for your help!

@lithiumpie
Copy link
Contributor

Hey~ @neighborhood999 I take faq-state

@neighborhood999
Copy link
Member

Hey~ @neighborhood999 I take faq-state

I updated list, thank you for help!

@huantingwei
Copy link
Contributor

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

@chloewlin
Copy link
Member

chloewlin commented Aug 24, 2020 •
edited
Loading

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.

@vrabe
Copy link
Contributor

vrabe commented Sep 28, 2020

Hello, I want to take Static Type Checking.

@chloewlin
Copy link
Member

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.

@henry61024
Copy link
Contributor

henry61024 commented Nov 6, 2020 •
edited
Loading

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

@bugtender
Copy link
Member

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

@huantingwei
Copy link
Contributor

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

@chloewlin
Copy link
Member

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

@henry61024
Copy link
Contributor

henry61024 commented Feb 12, 2021 •
edited
Loading

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?

@neighborhood999
Copy link
Member

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

@neighborhood999
Copy link
Member

I take the unknown-prop.

@rudy0628
Copy link

rudy0628 commented Dec 1, 2022 •
edited
Loading

I take the Virtual DOM and Internals

rickhanlonii pushed a commit that referenced this issue Apr 22, 2023
@renancouto
Fix legacy link (#1)
7863b5b
@gaearon gaearon changed the title Traditional Chinese Translation Progress [OLD] Legacy Traditional Chinese Translation Progress Apr 25, 2023
@gaearon
Copy link
Member

gaearon commented Apr 25, 2023 •
edited
Loading

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

@gaearon gaearon closed this as completed Apr 25, 2023
@gaearon gaearon unpinned this issue Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chloewlin chloewlin

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests