React: [New Docs] Set Up Localization Effort

[gaearon]

We've deleted the old localized content because most of the docs changed too much.
We should set up proper infrastructure for localization because the old process was slow and ineffective.

cc @lacker

[wong2]

Would you consider using something like: https://www.transifex.com/ ?

[gaearon]

I heard from @zpao that @thejameskyle was building something for Yarn which we may then reuse.

[lacker]

@ericnakagawa is going to work with @thejameskyle to see if the Yarn solution will work for React.

[gbezyuk]

@translation-gang is ready to help with Russian translation, as soon there will be an infrastructure.

[gaearon]

That’s pretty awesome. We will keep you posted!

[JisuPark]

AWESOME. Just tell @little-big-programming when infra is ready. I'll jump into Korean translation.

[ericnakagawa]

Hi folks, we are making steady progress on a workflow for community driven localization. We've helped get one OSS project (@yarnpkg/website) working using the system! We've learned a lot and things should move along rather quickly from this point.

I'm hoping @JisuPark @gbezyuk and others on this thread are still able to assist. Thanks!

[sophiebits]

Very happy to get localization in. What do you need from us?

[gbezyuk]

@ericnakagawa we totally are, just tell us what to do ;)

[JisuPark]

@ericclemmons Of course we are :) Just tell us what you need. Thanks.

[namkwon]

I wish I can do help for Korean localization. :)

[ferlopezm94]

Hi! I'd like to help for translating docs to Spanish. I've been searching for guidelines to do this but I couldn't find them.

[gaearon]

We haven't started the process yet. We'll write in this issue when everything is ready.

[gaearon]

@ericnakagawa @hramos Is there anything we can do on our side to start the process? I don’t want to lose valuable effort like https://discountry.github.io/react/ which will get out of sync soon.

[hramos]

@gaearon ping Eric directly, he's been leading the localization effort for other sites

[leocabeza]

Hi. Just writing here to let anyone know I can help with spanish translations. I'll be watching this issue.

[gaearon]

Thanks! There‘s ongoing work to begin accepting translations in the coming weeks.

[ryouaki]

I am a Chinese . (^_^)v

[discountry]

@gaearon Do we have any progress now? We've been kept updating our Chinese version docs to v15.6.1. And we are ready to catch up with the react@16 updates. When would there be any official localization plan to accept other languages translation?

[gaearon]

@bvaughn is working on a website revamp and we'll likely combine this with the localization setup effort. We might have something in a month or so. Stay tuned :-)

[ericnakagawa]

Hi folks, React documentation localization effort is ready for contributions.

Documentation is primed for localization. So far we've had great efforts from the Indonesian, Japanese, and Portuguese Brazilian communities.

Please direct interested members of your community to the official Crowdin project repo: https://crowdin.com/project/react

@discountry Would you be interested in helping manage Chinese?
@ryouaki Please sign up!
@leocabeza @ferlopez94 Happy to accept your folks help!
@gbezyuk Are you folks able to help lead Russian translation?
@JisuPark Are you still able to help with Korean?

If you have any questions, please message me here in this thread, on CrowdIn, or on Twitter @ericnakagawa!

[sophiebits]

cc past translations contributors @ivanzotov @alexzherdev @dotu @marocchino @zhangjg @kohei-takata @camsong if any of you are interested in helping with official translations

[gaearon]

What can I do to help with Russian translation? Happy to review etc.

[ericnakagawa]

@gaearon If you can review or help identify someone that can help manage reviewing that'd help this effort. It'll take some time to reach a high %.

[gaearon]

What do you generally recommend re: quality? Do we start with lower quality translations and iterate, or do we set a high bar from the beginning?

[ericnakagawa]

@gaearon Aiming for high quality initially is best!

[gaearon]

If there is a low quality translation, do we just wait for someone to contribute a better one? Reject it somehow?

[discountry]

@ericnakagawa I can help manage reviewing Chinese translation.

[FateRiddle]

@ericnakagawa I'd love to be part of Chinese simplified translation.
@discountry I love the current Chinese docs, and believe we can make the official one even better and concise. How do you prefer we contact and coordinate?

[discountry]

@FateRiddle Submit on CrowdIn or pull request to Chinese doc repo are both fine. We already have a group up to 50 members, you can find us on react-china.

[ericnakagawa]

@discountry Because of your work leading the Chinese React translation project I've added you as a reviewer!

[ryouaki]

I finished some translation about warnings, readme and others on CrowdIn.
@discountry we really have 50 members?

[keyz]

@ericnakagawa would you mind also adding me as a reviewer for simplified Chinese? Thanks :)

[discountry]

@gaearon We've deployed a Chinese version doc on a server in China at React Chinese Doc. Would you mind adding a link to it on the official react doc website later? Because of the network issues in China, it's very slow & inconvenient for Chinese users to visit a Github Pages site.

[smikitky]

@ericnakagawa Is there a convenient way for translators to test/preview the localized version before it's published? I'm seeing no download button on Crowdin, and the translations are pushed to nowhere on GitHub, right? Being able to check online is ideal, but I can install a local environment to build the docs.

[sophiebits]

@discountry Are sites that use cloudflare (ex: yarnpkg.com, babeljs.io) accessible easily? It would be great to have it all together.

[discountry]

@sophiebits actually cloudflare is very slow when visiting from China.

[ericnakagawa]

@smikitky Hi, the new website is currently being developed. We don't have a preview site configured yet, but once they new site design is live we'll be working to allow live previews!

[ericnakagawa]

@keyanzhang I've added you. Please check your email.

[ericnakagawa]

Hi folks, update on our translation progress.

Japanese: 100%
Indonesian/Behasa: 60%
Chinese Simplified: 56%
Portuguese Brazilian: 51%
French: 11%
Spanish: 11%
Greek, Korean, Russian, Danish, German, Arabic, Bengali, Ukrainian, Czech, Polish, Turkish: < 10%

Details here: https://crowdin.com/project/react/settings#translations

[JisuPark]

@ericnakagawa Hello, Korean translation is progressing slower than I thought, but I'm still working. What do you think about adding a glossary page? Even if we want to translate, it is hard to unify expressions or words. At least I want to bring Korean in a consistent way, can you give me advice?

[ericnakagawa]

@JisuPark How do you think having a glossary page would help? Where should that live?

[gaearon]

I think it would make sense to create a Glossary page in docs themselves. There was some initial work in https://github.com/facebook/react/pull/8199. If we got that through, that could help anchor translations as well.

[JisuPark]

@ericnakagawa I think Glossary page will be in the docs, same as @gaearon's opinion.
Glossary will help a not only person who wants to read official docs in their language but also guides people who want to translate other React related docs to use a general expression.

[smikitky]

A good glossary in the original document is desirable in the long run, but I think we don't have to wait for it. Japanese translators maintain a list of words so we can translate React jargon (such as "uncontrolled component") consistently: https://gist.github.com/smikitky/15f1332ec1d820b96159ccb56e6862a3

I'm saying this because making a glossary would be a nontrivial task. Forgive me to say this, but what I've found after reviewing the entire document was that the original document is not very consistent regarding the word usage. For example, <div /> is referred to as "DOM component" in one place, but "component" only refers to user-defined components in another place (e.g., "Always start component names with a capital letter."), while "custom components", "composite components" and "user-defined components" seem to be other (redundant?) synonyms used elsewhere. "React component" may or may not include <div>'s depending on the context. Nevertheless, even with these inconsistencies, all chapters are fully understandable and translatable if you have the basic knowledge of React. I doubt strictly consistent documentation is a priority of the core team; translators may have to move on without a "source-of-truth" glossary.

[bvaughn]

Migrating to reactjs/reactjs.org/issues/82

[gaearon]

We've launched our first translations, and many need more contributors.

https://reactjs.org/blog/2019/02/23/is-react-translated-yet.html