Russian Translation Progress

[tesseralis]

Текущий список мейнтейнеров

• 🥇 @lex111
• @gaearon
• @another-guy
• @Heegiiny
• @gcor
• @ntishkevich

Если у вас есть время и желание, и вы уже участвуете в развитии проекта, то можете создать пулреквест с добавлением своего логина в список мейнтейнеров в этом репозитории.

---

Как помочь с переводом

Вы можете перевести страницу из документации! Это делается в три шага:

1. Проверьте, что её никто не застолбил в чеклисте или комментариях под ним (они не сразу отражаются в чеклисте)
2. Напишите, какую страницу вы ходите перевести. Пожалуйста, не берите больше одной страницы за раз.
3. Когда страница готова, отредактируйте ваш комментарий, чтобы добавить номер пулреквеста.

Прежде чем переводить, обязательно прочитайте местные правила перевода!

Пожалуйста, не тяните с переводами! Если у вас не получается или нет времени, отпишитесь, чтобы кто-то другой мог подхватить эту страницу.

For maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

• [x] Home Page (@tesseralis) #1

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.

• [x] Home Page (@lex111)
• [x] Tutorial (@vvscode) #201

Basics

• [x] Hello World (@ModPhoenix) #2
• [x] Introducing JSX (@another-guy) #17
• [x] Rendering Elements (@Heegiiny) #11
• [x] Components and Props (@gaearon) #34
• [x] State and Lifecycle (@agoldis) #42
• [x] Handling Events (@dpatrikeev) #89
• [x] Conditional Rendering (@another-guy) #60
• [x] Lists and Keys (@Windrushfarer) #64
• [x] Forms (@thechch) #174
• [x] Lifting State Up (@rlax) #238
• [x] Composition vs Inheritance (@aamorozov & @gcor) #225
• [x] Thinking in React (@marichka-offen) #90

API Reference

• [x] React (@ModPhoenix) #66
• [x] React.Component (@gcor) #131
• [x] ReactDOM (@akhudiakov97) #126
• [x] ReactDOMServer (reassigned to @mikhail-hatsilau) #207
• [x] DOM Elements (@ivankayzer) #88
• [x] SyntheticEvent (@dmtrKovalenko) #122
• [x] Test Utilities (@shonoru) #97
• [x] Shallow Renderer (@Yakimych) #99, #110
• [x] Test Renderer (@theghostbel +-@ModPhoenix) #240
• [x] JS Environment Requirements (@kuhelbeher) #68
• [x] Glossary (@marichka-offen) #200

Navigation

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

• [x] tutorial/nav.yml
• [x] docs/nav.yml

Next Steps

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

Installation

• [x] Getting Started (@AlLevykin) #39
• [x] Add React to a Website (@shvedovskiy) #96
• [x] Create a New React App (reassigned to @ChernikAnton) #242
• [x] CDN Links (@lex111) #28

Hooks

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

• [x] Introducing Hooks (@pavelkeyzik) #84
• [x] Hooks at a Glance (@Hisagr) #65
• [x] Using the State Hook (@another-guy) #134
• [x] Using the Effect Hook (@Hisagr) #112
• [x] Rules of Hooks (@airyboy) #86
• [x] Building Your Own Hooks (@tesler) #150
• [x] Hooks API Reference (@polling) #226
• [x] Hooks FAQ (@egorzekov) #208

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.

• [x] dont-call-proptypes (@lex111) #143
• [x] invalid-aria-prop (@lex111) #144
• [x] invalid-hook-call-warning (@lex111) #145
• [x] legacy-factories (@lex111) #31
• [x] refs-must-have-owner (@vvscode) #119
• [x] special-props (@lex111) #32
• [x] unknown-prop (@another-guy) #212

Advanced Guides

• [x] Accessibility (reassigned to @AlLevykin) #239
• [x] Code-Splitting (@avevlad) #246
• [x] Context (@egorzekov) #164
• [x] Error Boundaries (@mzhukov1973) #73
• [x] Forwarding Refs (@Heegiiny) #117
• [x] Fragments (@ntishkevich) #120
• [x] Higher-Order Components (@agoldis) #167
• [x] Integrating with Other Libraries (@vvscode) #159
• [x] JSX In Depth (@RenatRysaev) #206
• [x] Optimizing Performance (@RenatRysaev) #141
• [x] Portals (@echobrain) #153
• [x] React Without ES6 (@DopustimVladimir) #177
• [x] React Without JSX (@vvscode) #118
• [x] Reconciliation (@astralpunch) #139
• [x] Refs and the DOM (reassigned to @SmolinPavel) #236
• [x] Render Props (@Azat74) #163
• [x] Static Type Checking (@acilsd) #166
• [x] Strict Mode (@ntishkevich) #178
• [x] Typechecking With PropTypes (@vvscode) #129
• [x] Uncontrolled Components (@lex111) #37
• [x] Web Components (~@mzhukov1973~ -> @ntishkevich) #234

FAQ

• [x] APIs and AJAX (@avevlad) #30
• [x] Babel, JSX, and Build Steps (@avevlad) #38
• [x] Passing Functions to Components (@marichka-offen) ~#95~ #108
• [x] Component State (@Nadjakoroleva) #36
• [x] Styling and CSS (@T1mofey1) #183
• [x] File Structure (@RinatRezyapov) #98
• [x] Versioning Policy (@DmitryMarkov) #171
• [x] Virtual DOM and Internals (@ivaneroshkin) #161

Contributing

Priority: Low

• [x] How to Contribute (@AlLevykin) #149
• [x] Codebase Overview (@BogdanDor) #427
• [x] Implementation Notes (@BogdanDor) #433
• [x] Design Principles (@echobrain) part 1 - #244, part 2 - #258

Components

Components in src/components that have some text in them.

• [x] CodeEditor
• [x] CodeExample
• [x] ErrorDecoder
• [x] LayoutFooter
• [x] LayoutHeader
• [x] MarkdownPage

Additional Translations

These are not the primary translation targets.

• [ ] Blog
• [ ] Community

[ModPhoenix]

I took this page in translation: Basics -> Hello World. Tonight will do PR.

upd

Here is my PR with the translation #2

[doasync]

This can help with translation: https://learn-reactjs.ru EDIT: I'm not the author

[lex111]

Hi @stsiushkevich,

You have done a lot of translation work, it's very cool! :+1: But would you like to join the official Russian translation? That was great... Moreover, why should we have two translations, let's join our efforts to create only one translation on React, what do you think about this?

[another-guy]

@lex111 @tesseralis I'd like to get a bit of coordination/direction here. Couple of questions:

• First: Should I wait until we decide whether we want to get the official translation based of the one by @stsiushkevich? Or is it okay to pick a page to translate now (if so, I'd pick the Introducing JSX tentatively)? Using existing progress will definitely save the translation time but will add the review time to make sure the info is up-to-date.

• Second: Are we willing to use Crowdin or not? I have no preference since I've never used that service in the past.

[lex111]

Regardless of the decision of @stsiushkevich, we will do our own translation, i.e. definitely not copy and paste, which is wrong and violates copyright. But this was a great collaboration, of course, so I hope for a favorable solution...

Regarding to:

• Or is it okay to pick a page to translate now (if so, I'd pick the Introducing JSX tentatively)?

Of course, you can already do the translation!

By the way, check out my partial translation (https://github.com/js-ru/react-ru), maybe this will help!

• Second: Are we willing to use Crowdin or not? I have no preference since I've never used that service in the past.

Crowdin will not be used, translation will be done via GitHub, it can be used as a starting point (if there is any translation there).

[another-guy]

@lex111 Thank you for clarification.

I'm removing the paragraph about Crowdin from this issue's description to avoid confusion among new contributors.

[tesseralis]

@doasync would you be interested in being a maintainer? You already have a lot of experience with this and we could use your guidance, and we would love to take advantage of the work that you've done already.

The advantage of an official translation is that it can be reached directly from reactjs.org -- not docschina, not learn-reactjs.ru. We're also planning on using a bot to automatically submit pull requests when there are updates to the master branch.

[lex111]

@tesseralis small amendment, @stsiushkevich is author learn-reactjs.ru, not @doasync.

[Heegiiny]

I will translate the Basics >Rendering Elements page.

upd: Pull request #11 with translation is created.

[gaearon]

I suggest a principle we should follow throughout the translations: https://github.com/reactjs/ru.reactjs.org/pull/6

[another-guy]

@gaearon I think the living word principle will make things a bit subjective. Yet I agree it's important to follow it to establish rapport with the readers and to win their attention. Thanks for raising the bar early in the process!

[gaearon]

I agree it's subjective and we should follow common sense. I'm mostly adding this so that we hold clear language as an explicit value — even if we can't always live up to it.

[tesseralis]

@gaearon Dan, do you want to publish a version of that in English for the other translations to reference?

[gaearon]

@tesseralis I'm not sure how much it applies to other languages. Russian is sufficiently different from English that noun-heavy phrasing gets clumsy. But that might not be a problem in e.g. French. I wouldn't be able to carry that nuance across.

[tesseralis]

Ah, gotcha! ^_^

[gaearon]

Я возьму Components and Props следующей.

[marichka-offen]

Can I help? I would like to translate Thinking in React

Update: PR #90

[gaearon]

Sure. Thanks.

[agoldis]

🙋🏻‍♂️ please assign me on State & Lifecycle @tesseralis @another-guy @lex111 PR ready https://github.com/reactjs/ru.reactjs.org/pull/42 Please update the issue body with a link. Thank you! 🥕

[Windrushfarer]

I'll get Lists and Keys @tesseralis @another-guy @lex111 PR #64

[avevlad]

Assign me on FAQ: AJAX and APIs

[dpatrikeev]

I'll take Handling Events

[another-guy]

Conditional Rendering is the next piece for me to work on.

I also had the audacity to update the issue's description with the following volunteers/assignments:

@agoldis -- State and Lifecycle
@dpatrikeev -- Handling Events
@another-guy -- Conditional Rendering
@Windrushfarer -- Lists and Keys

[pavelkeyzik]

Hi! Can I take "Introducing Hooks" page? #84

[thechch]

I'd very much like to help with "Forms", if possible.

[rlax]

I'd like to translate "Lifting State Up"

[akhudiakov97]

I'd like to translate API Reference > ReactDOM. Update PR: #126

[aamorozov]

I'll help with Composition vs Inheritance, or if that has been completed - Fragments.

[AlLevykin]

Hi! I'd like to translate Installation > Getting Started (getting-started.md).

[ModPhoenix]

@lex111 @gaearon Хотел бы взять следующую API Reference -> React

[dmtrKovalenko]

I'd like to help with. Я бы хотел взять SyntheticEvent 😊

[Nadjakoroleva]

Привет! Я бы хотела перевести FAQ * Component State 😎

[gcor]

Hi, i'd like to translate React.Component

[sqts]

Привет! Я бы хотел перевести Hooks at a Glance

PR: #65

[Michael-dyko]

Привет! Хотел бы взять на перевод ReactDOMServer

[avevlad]

Возьму faq: Babel, JSX, and Build Steps

[another-guy]

@avevlad каждый переводчик работает только над одной страницей в каждый момент времени. Ты хотел работать над "APIs and AJAX" (присвоено в списке). Снять с тебя API/AJAX и назначить Babel/JSX/Build steps или оставить всё, как есть?

[avevlad]

@another-guy оставь все как есть, дождусь мерджа и напишу в тред еще раз

[another-guy]

@avevlad извини, я не заметил, что у тебя открыт PR для предыдущей темы. Бери Babel/JSX/Build steps. :)

[avevlad]

@another-guy взял! Спасибо! :)

[T1mofey1]

I would like to translate Styling and CSS

[avevlad]

Возьму Code-Splitting, PR #38 ждем мерджа

[RinatRezyapov]

Привет! Я бы хотел перевести FAQ -> File Structure

PR #98

[ivankayzer]

Привет, хотел бы взять API Reference -> DOM Elements

PR #88

[shonoru]

Приветствую, возьму API Reference -> Test Utilities

PR #97

[kuhelbeher]

Привет, возьму API Reference -> JavaScript Environment Requirements

PR #68

[sqts]

Я возьму перевести Using the Effect Hook

PR: #112

[mzhukov1973]

Возьму Error Boundaries (error-boundaries.md).

Update: Translation is in PR #73.

[airyboy]

Беру Rules of Hooks PR #86

[shvedovskiy]

Hi, I'd like to take Add React to a Website

UPD: Pull Request #96.