-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Azerbaijani Translation Progress #376
Comments
I have taken Learn React |
@GasimGasimzada @azizaismayilova Could you please confirm whether you would be able to maintain and steer this translation effort? If not, please send a PR to remove yourself from https://github.com/reactjs/translations.react.dev/blob/main/langs/az.json — then we'd need to find new maintainers before proceeding. Thank you! |
@gaearon In case of not getting info from them, i would like to participate during translation as a maintainer. |
Sounds good — let’s give them some time to respond. Thanks! |
Hi @gaearon, I can spend time on maintaining the repo and helping with translations; however, at a limited capacity in comparison to the first time I did the translations. |
Hi again, @gaearon. I am trying to form a team of contributors to help with the translation. Can you please tell me how to add new people as contributors? I will add them in the repo myself (I think I still have admin rights) but not sure if any other place needs to be updated. @nasirmovlamov and @wamujlb are currently two people who are interested. I am also in contact with others. |
Hi @gaearon! I will work on this translation as well. Also, I am happy to review/edit others pr to help them with proofreading. |
@GasimGasimzada Please send a PR to edit https://github.com/reactjs/translations.react.dev/blob/main/langs/az.json. I will fix it so that it gets synced later today. |
Hi, I also want to help with the translation. |
I have taken Homepage and TopNav, I made pr for them, but I will fix based on our previous dictionary and commit again with fixes. fyi @GasimGasimzada @azizaismayilova |
I have taken |
Hi @nasirmovlamov ! Could you please start translating content in recommended order? As it is mentioned above Navigation and UI content will need some invasive changes. |
Hi @vugartaghiyev ! Can you please select the content that you want to work one (preferably in recommended section) and comment it here? İ will add your name to the selected content until @GasimGasimzada will add all of you to the maintainer list. |
Hi @azizaismayilova, I will take |
@vugartaghiyev Yes, sure! I will add your name then. |
@vugartaghiyev @nasirmovlamov @wamujlb please join the Discord to discuss some specific translation topics: https://discord.gg/9ugVdPuf |
I’ve changed how this works yesterday — basically just add people in Settings as admins to the repo. |
awesome will do thank! |
I have taken |
Okay, I added your name near |
Hello, please check new pr |
@nasirmovlamov You can pick it up while we review it in parallel. For the future, when you want to pick up a new page, edit the issue and tag your username next to the page name. |
Sure 👍 |
Hey! I would like to take Describing the UI |
Sure go ahead @Vug6r |
hello! |
I do not see any progress on translation. Is this thread dead? |
@gaearon if this thread still valid can you add me to the maintainer list. The progress here is going less than slow. |
@rarblack added you to maintainers list. Let me know which page you want to pick up. |
Maintainer List
For New Translators
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.
For Maintainers
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!
Main Content
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.
Learn React
Quick Start (@vugartaghiyev)
Installation (@nasirmovlamov)
Describing the UI
Adding Interactivity
Managing State
Escape Hatches
API Reference
react
: HooksuseCallback
useContext
useDebugValue
useDeferredValue
useEffect
useId
useImperativeHandle
useInsertionEffect
useLayoutEffect
useMemo
useReducer
useRef
useState
useSyncExternalStore
useTransition
react
: Components<Fragment> (<>)
<Profiler>
<StrictMode>
<Suspense>
react
: APIscreateContext
forwardRef
lazy
memo
startTransition
react-dom
: Components<div>
)<input>
<option>
<progress>
<select>
<textarea>
react-dom
: APIscreatePortal
flushSync
findDOMNode
hydrate
render
unmountComponentAtNode
react-dom/client
: Client APIscreateRoot
hydrateRoot
react-dom/server
: Server APIsrenderToNodeStream
renderToPipeableStream
renderToReadableStream
renderToStaticMarkup
renderToStaticNodeStream
renderToString
Navigation and UI
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 )When You're Ready...
After everything above is translated, add your language to
deployedLanguages
inSeo.tsx
of the original reactjs/react.dev repository.Secondary Content
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
Optional Content
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:
The text was updated successfully, but these errors were encountered: