Repository navigation
Malayalam Translation Progress #1
Description
Activity
I would like to take up the translation of the page Describing the UI/ Your First Component
@JACOBIN-SCTCS Please share your PR.
@gaearon I will take care of updating the issue at #2. Could you please close this issue.
Reacted by JACOB JAMES K and Shreyas Santhosh@asimkt I think I do not have permission to close this issue. can you do that
What was the purpose of creating a second issue? The issue needs to have "Translation Progress" verbatim in the title to get picked up by our translation progress website code. It also needs to have special comments like
<!-- MAIN_CONTENT -->which this issue has and yours doesn't.It seems like the main problem is that you don't have admin rights to the repo because you have not accepted the invite. Please accept the invite and then use this issue instead of #2. Alternatively, please accept the invite and close this issue, but then make sure that #2 has both the correct title and the special comments to get picked up by our script. You'd also have to rename this issue to not get picked up by the script.
Hope this helps!
Hi @asimkt, @adarshm07,
I would like to translate the learn/Installation page. Could you please assign me that?@dev-thakku Done. Please share your MR shortly.
Reacted by Jemshith T K@dev-thakku Done. Please share your MR shortly.
Could you please check the PR #6?
Reacted by Asim Kattum ThazhaHi @gaearon, @asimkt, @JACOBIN-SCTCS
I am interested in translatingAdding Interactivityand would like to take up the task.Hello @asimkt, based on our previous conversations in the old PRs, I have concluded that we need to create documentation for beginners who may have limited exposure to English and programming terminologies. Therefore, we should use simple Malayalam and focus on explaining things in a way that a non-technical person can easily understand, rather than just providing a word-by-word translation. Do you agree with this approach?
I also have a suggestion. If possible, we can create and maintain a glossary for common terminologies. This will make the documentation more readable and consistent.
eg:-
User - ആപ്പ് ഉപയോഗിക്കുന്ന ആൾ/ ഉപഭോക്താവ് / യൂസർ -(This is just an example. We need to discuss and finalize the most appropriate wording.)Reacted by Asim Kattum Thazha@Amjad-RA Totally agree on this point. 🙌
Let's create a glossary. I'm only curious about the timing of when to create. Sharing some thoughts: This is the current status of documentation for reference.
- Here, I've used common terms like
components,propas English words. Should we continue using that? Because eventually developers have to get all other contents in English. If we keep Malayalam words for that, they may have this extra learning curve.
These are the other common words I can think of which needs to be in a glossary:
- Application
- Mockup
- Design
- Programming
- Tutorial
May be we can cover some basic pages and get an alignment on the terminologies later? Otherwise, I feel like we may get delayed on the details instead of putting in the time and effort more efficiently. Once we've covered all the basics, will we create the glossary and share it with future contributors? Please share your thoughts.
Reacted by Amjad Rehman A- Here, I've used common terms like
I would like to take up translation of Importing and Exporting Components
Reacted by Amjad Rehman A and Asim Kattum ThazhaHi @asimkt and @adarshm07 ,
I would like to contribute by translating the page “Tutorial: Tic-Tac-Toe.” Could you please assign it to me?Reacted by Asim Kattum ThazhaHey @tzzkenz & @Midhun0312 welcome. Please free to do and raise the PR.
Reacted by Midhun M
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 like this:
This ensures your translation's progress is tracked correctly at https://translations.react.dev/.
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 - @asimkt feat(quickstart): Quick start page #11
Installation - @dev-thakku Translate learn/installation #6
Describing the UI
Adding Interactivity (@Amjad-RA)
Managing State
Escape Hatches
API Reference
react: HooksuseCallbackuseContextuseDebugValueuseDeferredValueuseEffectuseIduseImperativeHandleuseInsertionEffectuseLayoutEffectuseMemouseReduceruseRefuseStateuseSyncExternalStoreuseTransitionreact: Components<Fragment> (<>)<Profiler><StrictMode><Suspense>react: APIscreateContextforwardReflazymemostartTransitionreact-dom: Components<div>)<input><option><progress><select><textarea>react-dom: APIscreatePortalflushSyncfindDOMNodehydraterenderunmountComponentAtNodereact-dom/client: Client APIscreateRoothydrateRootreact-dom/server: Server APIsrenderToNodeStreamrenderToPipeableStreamrenderToReadableStreamrenderToStaticMarkuprenderToStaticNodeStreamrenderToStringNavigation 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)TopNav.tsx)When You're Ready...
After everything above is translated, add your language to
deployedLanguagesinSeo.tsxof 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:
ChildrencloneElementComponentcreateElementcreateFactorycreateRefisValidElementPureComponentOptional 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:
Maintainer List
This translation is maintained by:
If you want to become a maintainer, ask them to add you. If the original maintainers are no longer responsive, raise an issue in the main translations repository.