reactjs / az.react.dev Goto Github PK
View Code? Open in Web Editor NEW🇦🇿 React documentation website in Azerbaijani
Home Page: https://az.react.dev
License: Creative Commons Attribution 4.0 International
🇦🇿 React documentation website in Azerbaijani
Home Page: https://az.react.dev
License: Creative Commons Attribution 4.0 International
Should we translate "runtime" in Azerbaijani as "icra vaxtı" or keep it in the English version?
This issue is created to discuss if we should be using "siniflər", "class-lar", or "klaslar"? Currently, we have been using "klaslar" to refer to classes; however, this might not be the best option. I want to hear your opinions.
Comments in Azerbaijani are more than welcome!
Should it be "Problemleri Ayıraraq" or "Konsernaları Ayıraraq"?
I think it makes more sense to keep API as it is pronounced in English: https://www.youtube.com/watch?v=gZTn6AQDy1g
So, we should use suffixes like this:
Also make sure to write API, not APİ
English | Azərbaycanca |
---|---|
class component | klas komponent |
controlled component | kontrol olunan komponent |
click | tıklamaq |
context | |
component | komponent |
fragments | fraqmentlər |
functional component | funskional komponent |
portal | portal |
properties | parametrlər |
prop(s) | prop(lar) |
lifecycle | lifecycle |
ref | ref |
render | render etmək |
state (in context of React components) |
state |
state (in general context) |
vəziyyət |
stateful component | state-li komponent |
uncontrolled component | kontrolsuz komponent |
English | Azərbaycanca |
---|---|
accessibility | imkanlılıq |
anchor | anker təqi |
application | applikasiya |
array | massiv |
arrow function | arrow funkiyası |
asynchronous | asinxron |
attributes | atributlar |
bug | baq |
bundle | paket |
callback | |
child | uşaq |
class | klas |
composition | kompozisiya |
conditional rendering | şərtli render |
constructor | konstuktor |
crash | çökmə |
current | cari |
data | məlumat |
debug | dibaq |
declarative | deklarativ |
DOM | DOM |
elements | elementlər |
embedding expressions | |
expression | ifadə |
external plugins | xarici pluginlər |
extent | genişləndirmək |
extention | genişlənmə |
event handler | hadisə işləyicisi |
example | nümunə |
framework | freymvork |
guide | təlimat |
hierarchy | ierarxiya |
higher order function | yüksək dərəcəli funskiya |
immutability | dəyişməzlik |
imperative | imperativ |
implementation | tətbiq |
import | import |
inheritance | varislik |
initialize | inisializasiya |
instance | instansiya (computer term) |
interact | qarşılıqlı təsir etmək |
item | element |
keyboard | klaviatur |
library | kitabxana |
local | lokal |
map | uzlaşdırmaq |
maintainer | saxlayıcı |
mock | |
nested | |
node | nod |
note | qeyd |
operator | operator |
output | nəticə |
package | paket |
parent | valideyn |
pattern | pattern |
plain | sadə |
polyfill | polifil |
pooling | pulinq |
power | dəstəkləmək |
private | privat |
propagate | yaymaq |
refactor | refaktor |
reference | referans |
reset | sıfırlamaq |
reuse | təkrar istifadə |
runtime | icra müddəti |
stack | stek |
syntax | sintaksis |
technology stack | texnologiya steki |
tip | məsləhət |
Tick | |
tool | alət |
tutorial | dərslik |
UI | UI (not Azerbaijani İ) |
user | istifadəçi |
Web | Veb |
wrapped component | əhatə olan komponent |
native | nativ |
For the time being, aside from PRs and issues, in order to communicate more efficiently for things such as what words to use or just general talk, I have created a Discord server: https://discord.gg/qvySJTz.
Should we keep "pattern" in English or we can translate it as "şablon" in Azerbaijani and add to the Glossary in any case.
I have merged the style guide and localized the source codes, which is enough for now but it is important for us to translate this guide in Azerbaijani for newcomers.
To translate a page:
Before contributing, read the glossary to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find find that you can't commit any more, let the maintainers know so they can assign the page to someone else.
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
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
the corresponding sections are translated to do these.
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.
Priority: Low
Components in src/components
that have some text in them.
I am asking this because, currently I have translated these values and as I read through them, it makes it harder to catch the actual name of it. My suggestion it to keep singular values and add azerbaijani suffixes:
What do you guys think? In documentation and tutorial, we are already explaining what they are in Azerbaijani using simpler terms. So, I think explaining them in Azerbaijani while making people remember the naming this way would make future conversations easier in React community.
To translate a page:
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
To do before releasing as an "official" translation. Please translate these pages first.
Note that each section has an index page, which needs to be translated too.
Quick Start (@vugartaghiyev)
Installation (@nasirmovlamov)
Describing the UI
Adding Interactivity
Managing State
Escape Hatches
react
: Hooks
useCallback
useContext
useDebugValue
useDeferredValue
useEffect
useId
useImperativeHandle
useInsertionEffect
useLayoutEffect
useMemo
useReducer
useRef
useState
useSyncExternalStore
useTransition
react
: Components
<Fragment> (<>)
<Profiler>
<StrictMode>
<Suspense>
react
: APIs
createContext
forwardRef
lazy
memo
startTransition
react-dom
: Components
<div>
)<input>
<option>
<progress>
<select>
<textarea>
react-dom
: APIs
createPortal
flushSync
findDOMNode
hydrate
render
unmountComponentAtNode
react-dom/client
: Client APIs
createRoot
hydrateRoot
react-dom/server
: Server APIs
renderToNodeStream
renderToPipeableStream
renderToReadableStream
renderToStaticMarkup
renderToStaticNodeStream
renderToString
We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.
HomeContent.js
) (@nasirmovlamov )src/sidebar*.json
) (@nasirmovlamov )TopNav.tsx
) (@nasirmovlamov )After everything above is translated, add your language to deployedLanguages
in Seo.tsx
of the original reactjs/react.dev repository.
These API pages should ideally be translated too, but they're less urgent and can be done after the others:
Children
cloneElement
Component
createElement
createFactory
createRef
isValidElement
PureComponent
These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages:
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:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.