Awaiting Reviews

[GasimGasimzada]

In this issue, I would like others to review the following pages as a fresh set of eyes. You might catch things that I may have missed:

FAQ

• AJAX and APIs Fixes translations of FAQ section #172
• Babel, JSX, and Build FAQ Fixes translations of FAQ section #172
• Styling Fixes translations of FAQ section #172
• Virtual DOM and Internals Fixes translations of FAQ section #172
• File Structure Fixes translations of FAQ section #172
• Versioning Policy Fixes translations of FAQ section #172
• Component State Fixes translations of FAQ section #172
• Passing Functions to Components Fixes translations of FAQ section #172

Advanced Guides

• Refs and the DOM
• Render Props
• Profiler API
• Optimizing Performance
• Reconciliation
• Strict Mode
• Static Type Checking
• Uncontrolled Components
• Typechecking with PropTypes
• React without ES6
• React without JSX
• JSX in Depth
• Portals
• Integrating with Other Libraries
• High-Order Components

Testing

• Testing Overview
• Testing Recipes
• Testing Environments

Hooks

• Hooks Intro
• Hooks Overview
• State Hook
• Effect Hook
• Rules of Hooks
• Custom Hooks
• Hooks API Reference
• Hooks FAQ

Contribution

• How to Contribute
• Implementation Notes
• Codebase Overview

Concurrent Mode

• Suspense for Data Fetching
• Concurrent UI Patterns
• Concurrent Mode Adoption
• Concurrent Mode API Reference

[mehdiyev]

• Babel, JSX, and Build FAQ

• How about using "Xeyr!" instead of "Yox!"?
• How about using "yazılır" instead of "gedir"? As {/* Komment bura yazılır*/}

• Styling

• Komponentlərə CSS siniflərini necə əlavə edə bilərəm? There are no upper cases in original. Also, check all other headings. One more thing, here "I" subject was used (bilərəm) but in some documents such as Passing Functions to Components there is no subject (Funksiyanı komponent instansiyasına necə bind etmək olar?) in translation (actually, there are both way translations in first two headings in Passing Functions to Components doc.). So, how about translating it as Komponentlərə CSS siniflərini necə əlavə etmək olar? and try to keep one single convention.
• I think here should be comma: Əgər yuxarıdakı formalı kodu çox yazırsınızsa,
• In Conditional Rendering documentation "inline" was translated as "sətirdaxili" but here as "eyni-sətrli".
• I suggest "stillərdən daha performanslıdır." instead of "stillərdən daha tez işləyir."
• In sentence "JavaScript-də tərtib edilməsi metodu" feels like we are losing context. How about using phrase like "JavaScript ilə" or "JavaScript istifadə edərək"?
• Another incompatibility between documents: "üçüncü tərəf" instead of "3-cü tərəf"
• Just a suggestion, how about using "göstərə bilərsiniz" or "istifadə edə bilərsiniz" instead of "istinas edə bilərsiniz". Just seems like unnecessary complicated word.

• Virtual DOM and Internals

• Again, no upper cases in original doc.
• "proqramçılar" instead of "adamlar"
• "Xeyr" instead of "Yox"

[GasimGasimzada]

@mehdiyev Thank you for your contributions! Could you please create a PR with the changes that you have written here?

[mehdiyev]

Is that right translation "string" as "mətn"? "mətn" is more like "text" than "string". Isn't it misleading?

[GasimGasimzada]

This is something that I decide based on the fact that there is really no translation for string in Azerbaijani. Some people say "simli" but it creates more confusion because. String actually stands for "string of characters." Even though I know that it actually means "text," I chose "mətn" because it is the closest that I could think of a data / scalar type that represents a string of characters.

I am very open to suggestions on this matter.

[mehdiyev]

• What about not translating it? I mean, we can use original as we did with words such as "rekursiv", "render", "throttle" and so on.

• Or we can consider translating it with change to avoid lost in translation. For example, some combinations like "simli mətn", "simvol simi", "mətn məlumat növü" or "xarakterlər seriyası".

[GasimGasimzada]

@mehdiyev

Or we can consider translating it with change to avoid lost in translation. For example, some combinations like "simli mətn", "simvol simi", "mətn məlumat növü" or "xarakterlər seriyası".

Let's keep them until we are 100% done with the docs, which is very close. Then, we can come to some kind of agreement on what to do next.

[GasimGasimzada]

@mehdiyev what do you think of translating the term development to "təkmilləşmə"? My only concern is that it can create confusion. Otherwise, I think it is a good translation of the word "Development"

[mehdiyev]

What about "təkmilləşdirmə"? Btw, we also should consider connected term"developer". Translate it as "proqramçı" or "təkmilləşdirici"?

[GasimGasimzada]

For the term developer, I have done it in a lot of places. I think the only place where I haven't done it is when the term is "developer tools" or something similar.

What about "təkmilləşdirmə"?

doesn't matter. whichever works best based on context.

[mehdiyev]

Okay then. I think it is good translation and I feel like we shouldn't be worried about confusion. Azerbaijani is not rich with technical terms but it should and it is getting updates by time. And we are part of it. ReactJS is a very popular lib and its documentation can be used as reference for translations of tech terms. So, we can kind of start with new translation of tech terms, aware or unaware. And with new terms of course will be some confusions at the beginning till community accepts it.

[GasimGasimzada]

@mehdiyev I have been thinking about the word "string" and what do you think of "simvollar ardıcıllığı" or "simvollar simi"?

[mehdiyev]

@GasimGasimzada I think "simvollar simi" is better. It contains word "sim" which is literal translation of "string" and it is more specific.