Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Japanese Translation Progress #4
For New Translators
To translate a page:
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!
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".
To do before releasing as an "official" translation. Please translate these pages first.
These are the navigation links that appears in the sidebar. Possibly wait until
These are the next most important translations, ordered by importance:
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.
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.
These are not the primary translation targets.
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.
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.