-
Notifications
You must be signed in to change notification settings - Fork 119
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 Ukrainian Translation Progress #457
Comments
Hi, I would like to translate |
Hi! I would like to translate |
Hi, there. I would like to translate |
Hi! I would like to translate Done in #458 |
I would like to translate |
I'd like to take |
Hi! I would like to translate Done in #460 |
@vldmrkl @ithompson4 @oleksii-polovyi @MargarytaChepiga Can you please confirm whether you'd be able to steer and maintain this translation? If not, please let us know by updating https://github.com/reactjs/translations.react.dev/blob/main/langs/uk.json so that we know who is active and can set the GH permissions right. Thank you! |
Hi, I'd like to take |
Hi there. I would like to translate Done in #468 |
Hi, I'd like to translate Done in #459 |
Hi, I'd like to translate |
Hey! I'd like to translate |
@vldmrkl @ithompson4 @oleksii-polovyi @MargarytaChepiga Can you please confirm whether you'd be able to maintain this translation? Totally understand if not, but in that case we'd need to form a new maintainer team first. Thank you! |
I'll start translating |
Hi, I'll start translating It's done in #464 |
Hi folks, While I appreciate everyone’s requests to take a piece of the translation, the main issue right now is that it doesn’t appear that anyone on the original maintainer team is able to steer this translation effort. Would anyone like to volunteer to do that? |
Well, then I'd like to try |
@bkatsevych Do you have some experience doing translations? We'd like to ideally either have maintainers who've done translations before, or to have more than one maintainer per translation. |
@gaearon No, unfortunately I don't. But I'm willing to do my best |
Alright, let's give it a try. I've added you to the repo. Thanks! |
@eugenetree, go for it! |
@PavelVyny go for it! |
@sergii-zhuravel it's yours, go for it! |
@dolynchuk Sounds good, go for it! |
@gymnasy55 Go for it! |
@bkatsevych Please also edit the post to include who's working on what. |
Working on |
Working on |
Working on |
@dolynchuk @gymnasy55 @sergii-zhuravel @Kamilius @EngiN33R @PavelVyny @eugenetree @harddownloader Please, respond with any emoji to this comment if you're planning to finish your articles in the near future. Also you're welcome to change an article by leaving a comment if you want so. |
Working on |
@dolynchuk @gymnasy55 @sergii-zhuravel @Kamilius @PavelVyny @eugenetree @harddownloader Your articles were unassigned because you did not respond to the related comment above in time. Nevertheless, we are glad to welcome you back if you wish to translate articles in the future. |
Hi there, I would like to translate |
Hi, I'd like to translate Render and Commit |
I've created discord group https://discord.gg/WM6PmCpp7W to facilitate communication about Ukrainian technical translations, including work on React documentation. Feel free to join @bkatsevych FYI |
Hello, there! cc: @alinkedd |
Ima translate the "adding interactivity" page. |
Thanks for the quick PR. Unfortunately, I wasn’t fast enough to mention that your section intro page ‘Adding Interactivity’ includes vocabulary, references, and examples from subpages. It would be better to translate these first and then use that content in your page for the sake of consistency and ease. I will keep this PR as a draft until all or almost all internal articles are translated. Nevertheless, I’m going to add some general feedback regarding common mistakes to help you get started with our translation process. Please translate the subpages first next time. If you have any questions, feel free to ask me on Discord: https://discord.gg/WM6PmCpp7W. |
Got it, I am new to it. So feel free to take over whenever you think it's suitable (If you can do that on GitHub, of course). Otherwise, I'll start applying your feedback to the subpages right away. I would like to translate the “Updating Objects in State” Subpage next. |
I'd like to translate “Start a New React Project” |
I'd like to translate “Editor Setup” |
I'd like to translate “State as a Snapshot” (my todo) |
I'd like to translate “Queuing a Series of State Updates” |
@undead404 okay, and please, first check my review on the Editor Setup so we encounter fewer issues later |
Hi, there! I'll take "Updating Arrays in State" |
@astropsy999 Okay, thanks for your effort! |
I'd like to translate "Reacting to Input with State" |
@undead404 thanks of choosing other subpage article instead of chapter introductory page. Here is an explanation - #457 (comment). You may finish Managing State, when subpages are ready. |
I'd like to translate "Choosing the State Structure" |
I'll translate "useContext" |
Next I'll take "Scaling Up with Reducer and Context", because there is a link to it in the previous one |
Hi there, I would like to translate |
Hi 👋, I'd like to translate "Extracting State Logic into a Reducer" |
Maintainer List
(Updated on 2024/08/23)
@vldmrkl@ithompson4@oleksii-polovyiActive translators:
For New Translators
To translate a page:
Before contributing, read the glossary and style guide 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.
(Updated on 2024/12/10)
Learn React
Quick Start (@stanislavcodes) Finished translation of Quick Start page #466
Installation (@alinkedd) Finished translation of Installation page #500
Describing the UI (@alinkedd) Finished translation of Describing the UI page #513
Adding Interactivity (@MinichMykyta) Translated "adding interactivity" page #539 - waiting for subpages to be translated
Managing State
Escape Hatches
API Reference
React Reference Overview
react
: HooksuseActionState
(useFormState
)useCallback
(@poznianski)useContext
(@astropsy999) useContext.md finished #560useDebugValue
useDeferredValue
useEffect
useId
useImperativeHandle
useInsertionEffect
useLayoutEffect
useMemo
useOptimistic
useReducer
useRef
useState
useSyncExternalStore
useTransition
react
: Components<Fragment> (<>)
(@syavik2001) (Finished translation of Fragment page #460)<Profiler>
(@GeorgeShvab) (Finished translation of Profiler page #564)<StrictMode>
<Suspense>
(@GeorgeShvab) Finished translation of Suspense page #556react
: APIsact
cache
createContext
forwardRef
(@GeorgeShvab) (Finished translation of forwardRef page #473)lazy
memo
startTransition
use
experimental_taintObjectReference
(under construction)experimental_taintUniqueValue
(under construction)experimental
react-dom
: HooksuseFormStatus
react-dom
: Components<div>
)<form>
<input>
<option>
<progress>
<select>
<textarea>
<link>
<meta>
<script>
<style>
<title>
react-dom
: APIscreatePortal
(@GeorgeShvab) (Finished translation of createPortal page #468)flushSync
findDOMNode
hydrate
(@GeorgeShvab) (Finished translation of hydrate page #503)preconnect
prefetchDNS
preinit
preinitModule
preload
preloadModule
render
unmountComponentAtNode
react-dom/client
: Client APIscreateRoot
hydrateRoot
react-dom/server
: Server APIsrenderToNodeStream
renderToPipeableStream
renderToReadableStream
renderToStaticMarkup
renderToStaticNodeStream
renderToString
react-dom/server
: Static APIsprerender
prerenderToNodeStream
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
)src/sidebar*.json
) (@undead404) Translate titles in sidebar for pages already in Ukrainian #551 + every next article should be shipped with its title changed in the sidebar; in progressTopNav.tsx
)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:
Rules of React
React Server Components
'use client'
'use server'
Legacy APIs
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: