Japanese Translation Progress
tesseralis opened this issue · comments
For New Translators
To translate a page:
- Check that no one else has claimed your page in the checklist and comments below.
- Comment below with the name of the page you would like to translate. Take only one page at a time.
- Submit a PR!
Please check the style guide and word list to make sure translations are written in a consistent manner.
Also check out the Crowdin repository before starting translation of a new article. Click and open each article to see how much work has been actually done. "0%" in the index page does not mean the article has not been translated!
For Reviewers
Before starting your thorough review, please make a comment in the individual PR page so that too many duplicate suggestions/comments will not happen at the same time. "Reviewers" section at the right means "those people will review eventually".
Work List
(🏃 Work in Progress; 👀 In Review)
Core Pages
To do before releasing as an "official" translation. Please translate these pages first.
- Home Page (@superyusuke) #55
- Tutorial (@smikitky) #144
Basics
- Hello World (@smikitky) (direct commit)
- Introducing JSX (@smikitky) (direct commit)
- Rendering Elements (@smikitky) (direct commit)
- Components and Props (@smikitky) (direct commit)
- State and Lifecycle (@smikitky) (direct commit)
- Handling Events (@smikitky) (direct commit)
- Conditional Rendering (@smikitky) (direct commit)
- Lists and Keys (@smikitky) (direct commit)
- Forms (@smikitky) (direct commit)
- Lifting State Up (@sasurau4) #15
- Composition vs Inheritance (@Naturalclar) #5
- Thinking in React (@Nkzn) #16
API Reference
- React (@lightnet328) #47
- React.Component (@lightnet328) #127
- ReactDOM (@gotchane) #45
- ReactDOMServer (@sasurau4) #114
- DOM Elements (@kn3ny) #12
- SyntheticEvent (@summertree128) #43
- Test Utilities (@takanorip) #57
- Shallow Renderer (@sakito21) #56
- Test Renderer (@queq1890) #11
- JS Environment Requirements (@saitoeku3) #9
- Glossary (@potato4d) #2 #21
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
- Getting Started (@Naturalclar) #63
- Add React to a Website (@sato11) #19
- Create a New React App (@kik4) #14
- CDN Links (@kik4) #13
Hooks
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.
- Hooks (@smikitky)
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.
- Warnings (@uehaj) #50
- dont-call-proptypes
- invalid-aria-prop
- legacy-factories
- refs-must-have-owner
- special-props
- unknown-prop
- invalid-hook-call-warning (new)
Advanced Guides
- Accessibility (@sasurau4) #99
- Code-Splitting (@atsumine) #58
- Context (@locol23) #59
- Error Boundaries (@uenitty) #81
- Forwarding Refs (@satotake)
- Fragments (@shooontan) #92
- Higher-Order Components (@satotake) #103
- Integrating with Other Libraries (@thayashi) #117
- JSX In Depth (@sato11) #62
- Optimizing Performance (@uehaj) #122
- Portals (@fsubal) #44
- React Without ES6 (@ginpei) #53
- React Without JSX (@hassi32) #62
- Reconciliation (@km-tr) #101
- Refs and the DOM (@y-temp4) #52
- Render Props (@ossan-engineer) #49
- Static Type Checking (@Naturalclar) #179
- Strict Mode (@notherno)
- Typechecking With PropTypes (@Naturalclar) #67
- Uncontrolled Components (@kik4)
- Web Components (@Naturalclar) #102
FAQ
- AJAX and APIs (@ossan-engineer) #10
- Babel, JSX, and Build Steps (@ossan-engineer) #93
- Passing Functions to Components (@ossan-engineer) #111
- Component State (@ginpei) #105
- Styling and CSS (@Naturalclar) #104
- File Structure (@syug) #120
- Versioning Policy (@37108) #121
- Virtual DOM and Internals (@syug) #132
Testing 🆕
- Testing Overview (@taneba) #241
- Testing Recipes (@smikitky) #261
- Testing Environments (@smikitky) #262
Contributing
Priority: Low
- How to Contribute (@oimo23) #123
- Codebase Overview (@thayashi)
- Implementation Notes (@y-yeah) #178
- Design Principles (@hand-dot) #133
Components
Components in src/components that have some text in them.
- CodeEditor @potato4d
- CodeExample @potato4d
- ErrorDecoder @potato4d
- LayoutFooter #151
- LayoutHeader
- MarkdownPage
Additional Translations
These are not the primary translation targets.
- Blog
- Community
I'd like to work on Composition vs Inheritance
@Naturalclar Thank you! Probably you can use the Crowdin's work as a base. We have not established a formal reviewing process, but once you've made a PR, I or someone will take a look.
As a model of translation, I think I want to work on a tutorial
@potato4d have you finished the glossary yet?
After I finished translating glossary, it was meant as an example of translation of that glossary!
I'd like to work on Lifting State Up 👍
@potato4d Tutorial is one of the longest (and the most outdated) articles, and I believe your top priority for the next few days is to set up the bot. According to this comment, we need to establish a good workflow in a few days. Do you think you can handle both?
@sasurau4 Thank you!
For now,
- Please do NOT modify link URLs in the original markdown even if there is a Japanese equivalent (using the Japanese version of an MDN/Wikipedia article, etc)
- Please do NOT worry about anchor names, just translate the heading text (reactjs/react.dev#1608). This means some inter-page links won't work now, but we'll fix this afterwards.
@smikitky I think you can edit my issue with these additional notifications.
Why shouldn't we translate the external links? I'm curious because someone on the Spanish translation team was asking.
@tesseralis I just wanted to play it safe until members of all forks reach some consensus about this :) We may come up with some automated solution.
I don't think so... It depends on whether those links exist / are high quality in each language, right? Like, Japanese Wiki might have a good article on "declarative programming" but maybe Russian doesn't?
Will think of a way to do general translation guidelines.
@potato4d do you have any thoughts from your experience with vue?
This is something we have to eventually discuss in the main repo. But React doc currently has literally hundreds of English-only external links (to Stack Overflow questions, YouTube videos, personal blog articles, Tweets, etc), which is atypical as the official documentation of a large library. I feel changing only a small part of them on an ad-hoc basis might not be a manageable option at least in the short term.
Sure, do you want to leave a comment on the main issue? Or if you want it to just be among translators I created a parent group for the internationalization effort: https://github.com/orgs/reactjs/teams/reactjs-org-internationalization
I don't think it's "ad hoc" to have the rule:
"If this link is for technical documentation and there is a high quality translation, link to the translation. Otherwise, keep the original English link."
There are copious links to non-translateable things like YouTube videos and StackOverflow and I think that is a issue to be handled by the English repo writers, but I don't think that should be a blocker.
@smikitky
Since it seems better to prioritize the setting of Bot, it may be better to ask smikitky for the tutorial.
Could you please?
In the case of Vue document, when I find a document translated by MDN etc., I am changing the link.
For example, most people reading Japanese documents are Japanese.
And, in most cases the Japanese are seeking Japanese document.
I just submitted a pull request to introduce TextLint.
If you have an opinion, please comment.
Okay, I'll take care of the tutorial.
May I take Thinking in React ?
@Nkzn Yes, please!
May I take React and React.Component?
@lightnet328
Yes, please!
thanks!
Can I take FAQ ?
Could I take JS Environment Requirements ?
I'd like to work on Shallow Renderer
@saitoeku3 @sakito21 Thank you!
I have some questions.
- Why we should check the old translation? I think it is too old.
- How do we check the quality of the new translation? How is the reviewer determined?
If I shouldn't discuss here, change the place.
Home page ってまだ空いてますか？やります。
I have some questions.
- Why we should check the old translation? I think it is too old.
- How do we check the quality of the new translation? How is the reviewer determined?
If I shouldn't discuss here, change the place.
これ自分も賛成で、React のドキュメントは、初学者が最初に読む重要な資料なので、学習資料として意味が通る翻訳にしたいという思いがあるのですが、そういったクオリティチェックに関しては今の所どんな感じでしょうか？
@takanorip @superyusuke Thank you for your interest.
- It depends on the article you're referring to. Some pages are already nearly 100% complete on Crowdin. In addition, the translation there are more or less reviewed with consistency in mind by more than one person, so it's safer to start based on it whenever possible. Still, you can always ignore some (or all) of them if you want.
- This fork started yesterday, and there is no established workflow yet. Tentatively, @tesseralis assigned me as the primary reviewer/maintainer, and I am willing to check every PR. I was also the person who once completed the translation at Crowdin. Honestly speaking, I did not expect this enthusiasm, so someone who wants to focus on quality assurance can nominate themselves as a dedicated reviewer.
My top priority is to make a translation guide (including style guideline).
May I work on Test Renderer?
@takanorip @superyusuke
(As additional information) see #2 and #6 and #3
If you have an opinion, please comment!
@ossan-engineer Sorry for the late reply. よろしくお願いします.
@superyusuke Thank you. ホームページとなると一段厳しくみんなでクオリティチェックされる可能性が高いのでレビューは気長にお付き合いください。
@queq1890 Yes, thank you!
Can I take DOM Elements?
May I work on ReactDOM?
May I work on ReactDOMServer?
@smikitky
Thanks for your answer.
I translate some documents and review other translation for now.
I will translate Test Utilities.
I'd like to work on Installation (getting-started.md)
Contributing seems to be done p much already on crowdin.
May I work on SyntheticEvent ?
Hi everyone!
I'm simply amazed at the incredible effort you've put in so far. I updated the issue with a stronger guideline on the rest of the sections, as suggested by @gaearon.
@ossan-engineer, the FAQ is composed of multiple sections. Could you start off with one and open up the rest to other people?
Hi!
May I take "Add React to a Website" ? If there is other parts to be worked, please inform me.
@uehaj Could you take one of the "warnings" first? These are the pages that are linked in the console warnings that happen, and they're useful for people to look up!
@uehaj Could you take one of the "warnings" first? These are the pages that are linked in the console warnings that happen, and they're useful for people to look up!
I got it! Ill tackle the ones.
May I take CDN Links and Create a New React App ? (CDN Links is too short and is already finished.)
@tesseralis Sure! I'm starting off with faq-ajax. I'd really aprreciate it if you list and open up other FAQs.
@summertree128 @uehaj @kik4 Updated the list. よろしくお願いします
素晴らしい。
一昨年のCrowdInでは作業者が数人しか居なかったけど、今回はこんなにContributeする方々が居るとは！
@smikitky
自分もまた時間作って翻訳に参加させて頂きます。
Hi everyone!
I'm thrilled to see what's going on here and I'd really like to lend a hand.
Just wondered: @uehaj are you taking the whole Warnings section? If it's too much work to be done during this weekend, tell me so I can be of help.
@tesseralis @smikitky
While waiting for his answer, I'm working on Add React to a Website part as it seems vacant. Okay with you?
Added the list of Advanced Guide / Contributing articles you can work on this weekend :)
@sato11 Thank you, assigned you to add-react-to-a-website. Each page under warnings are relatively small, so one person might handle that.
May I take Portals in Advanced guides ?
@fsubal 渋いチョイスですねｗ よろしくお願いします
So are we stepping into advanced section?
Having finished the draft above I'd like to take JSX In Depth part, may I?
@sato11 Yes, translating Advanced Topics was an extended goal, but since we've already run out of articles in Basics, I think we can move on.
May I take Fragments in Advanced Guides?
@shooontan Yes, thank you!
May I take Refs and the DOM in Advanced Guides?
Hi. May I take Code Splitting in Advanced Guides?
May I take Error Boundaries in Advanced Guides?
May I take Context in Advanced Guides?
Hi I'd love to join. Can I take React Without ES6 in Advanced Guides?
Hi, can I take Render Props ?
I'm thrilled to see what's going on here and I'd really like to lend a hand.
Just wondered: @uehaj are you taking the wholeWarningssection? If it's too much work to be done during this weekend, tell me so I can be of help.
Sorry for late responding and thanks for consideration. I have done whole warnings section.
Textlint is passes the last PR commit.
Hi, can I take React Without JSX in Advance Guides?
May I take "Optimizing Performance" ?
主にレビューでご協力くださっている方へ：
「今からレビューをするぞ」というところで、そのように個別のPRページ上で宣言していただくようお願いします。レビューはとても大切ですが、2人が全く同時にレビューすると「同じ指摘が重複して単純に労力の無駄」「コメント量が約2倍になって見づらい」「万一指摘が矛盾していたときに面倒」といったことになりがちですので、まずは1名が宣言した上で全体のレビューをしっかりやるのが効率的だと思います。その分少しだけレビュープロセスが長くなる可能性がありますがご了承ください。
CC @koba04 @potato4d @takanorip @sasurau4
（とはいえこんな心配しないといけないのはとても有り難いです）
@smikitky
方針に賛成です。
一方で、一人だけでは気づかないこともあるはずなので、せっかく今 2 Appove がマージ条件になっていることも活かして、 Approve を出したタイミングで別の人が見るという流れを基本とすると効率的かなぁと思いますが、いかがでしょう？
つまりは以下のフローとなります。
- レビュアー A レビュー宣言
- レビュアー A レビュー
- 作業者 レビュー対応
- (2〜3を繰り返し) レビュアー A Approve
- 1〜4をレビュアー B が行う
- マージ
とはいえ今レビューに貢献くださっている人は Approve 権限がない人もいるはずなので、その場合はコメントで代替するなどになるかとは思います。
@potato4d まあ厳密ではなくても、「1人目がまず全体をちゃんと見るまで他の人は待つ」みたいな意識が共有できていればうまく動くかなと思います。私のところで作業をとどめすぎるのは良くないので、Approveはそこまでの流れを眺めて総合的に「これなら大丈夫」と判断してやります。
Approve は一応個人のオピニオンとして持っておいたほうが安全かなぁという印象がありました。特に件数が増えてくると重複してる部分を見るのが怪しくなりがちなので、誰かのレビュー(というよりその人からのレビュー対応)が落ち着いた頃にやったほうが、作業者の心理的にも優しそうな気がしています
レビュー中か示すのは、コメントだと見落としが発生しそうなので、ラベルをつける運用でどうでしょうか？
「in review」というラベルを作ってみました。
レビュー開始時に付与して、レビューが終わった(Approveした)ら外す形で。
とりあえず #61 に移動して続けましょう…
Could I take dont-call-proptypes in the Warnings section?
Edit
Actually, I saw that dont-call-proptypes is already being reviewed in #50.
Could I take Typechecking With PropTypes instead?
I'll work on Rules of Hooks !
@Sasurau Hooks-related articles have been already translated, so could you choose another article?
@smikitky Oh, I misunderstood! 💦
I take Accessibility instead.
Hello, could I work on Strict Mode on Advanced Guides?
I'd like to work on Web Components
Hi, can I take Babel, JSX, and Build Steps ?
Hi all! I just synced from the original repo and there's some files that need re-translating! (Look for the <<<<<< HEAD comments)
#91 で、先週のフォークからの1週間で upstream (本家 reactjs.org) で起きたドキュメントの更新に対応するコミットが大量にマージされます。が、とりあえず翻訳絡みで影響があるのは Test Utils (#57, @takanorip) とフック絡みの各種記事 (@smikitky) のみです。他の方は現在の作業をそのまま続けて問題ありません。よろしくお願いします。
Can I take Reconciliation ?
@km-tr よろしくお願いします。Crowdinの翻訳をベースにする場合「突き合わせ」という訳語が使われていると思いますが、「更新検出処理」ないし「リコンシリエーション」で行くことになりましたのでご確認願います。
https://github.com/reactjs/ja.reactjs.org/wiki/%E8%A8%B3%E8%AA%9E%E3%81%AE%E7%B5%B1%E4%B8%80
Hi, can I take Passing Functions to Components ?
reactjs/react.dev#1608 と、それに対応する #96 の作業が完了し、すべての見出しに明示的にアンカー名が入るようになりました。以下のようなシンタックスです。これにより、ページ間・ページ内のすべてのリンクがURLを全く変えずに動作するようになります。
## Try React {#try-react}
### What does const [thing, setThing] = useState() mean? {#destructuring}
翻訳する時は、アンカー部分はそのまま残して、見出し本文のみを翻訳してください。
## React を試す {#try-react}
### const [thing, setThing] = useState() という記法の意味は？ {#destructuring}
まだ master にマージされていない PR をお持ちの方は、ちょっとしたコンフリクト解決作業をお願いします。大きな改変なので、ブランチの rebase と force-push による作業がお勧めです。殆どの方には釈迦に説法で申し訳ありませんが、こちらでも軽く説明しています。お手数ですがよろしくお願いします。
本日朝時点までにマージ済みの翻訳については、既にアンカーが付いていますので特段の作業は不要です。
これで無事 v16.8 リリース（Hook 導入）と ID 導入という大きな作業を乗り越えたので、当面は大きな改変はそうそう起きないと思います。よろしくお願いします。
Excellent work everyone! We're almost done with the core pages!
@lightnet328 @euxn23 how is the progress on your pages? It's been a while, if you are unable to complete those, please let us know so we can reassign those to other people.
I'd like to work on Styling and CSS
I would like to translate Higher-Order Components section.
I'd like to work on Static Type Checking
I'm going to take Component State in FAQ.
I'm going to open up ReactDOMServer since @euxn23 hasn't responded. Would anyone like to take it?
I'd like to work on Virtual DOM and Internals
May I take Uncontrolled Components?
May I take Integrating with Other Libraries?