-
Notifications
You must be signed in to change notification settings - Fork 123
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
[OLD] Legacy Hindi Translation Progress #1
Comments
@saranshkataria I am starting with Tutrial page |
@tesseralis @arshadkazmi42 @saranshkataria How can we differentiate that what all pages among the list have already been done ? |
@apoorvtomar2222 If any page is completed, it will has a check mark like below
|
if you would like to work on any of the page translation you can comment here with the page name and we will assign that page to you. |
@arshadkazmi42 I am picking up the home page. @apoorvtomar2222 feel free to pick anything else apart from the homepage or tutorial. I think it would be great if we go sequentially though. |
I would like to work on Hello World page. |
Go ahead |
@saranshkataria Home Page is still not completely translated. I have unmarked it as done.
We will mark it as done, when all these are also translated. |
@arshadkazmi42, I had mentioned in the PR that it is not complete. I wanted to put something in to kick things off. I know about the remaining sections. I had never marked it as done initially because of that. Working on those sections. Thanks though. |
Ok cool. I thought you missed it. We will add tick mark to every item once its {{done done}} |
They are in the home page. Also, should we split these into multiple issues instead of just one? |
I think this is fine. To keep track for all the Pages. Also, I am trying to get more contributors to help us with the translations |
@arshadkazmi42 the home page is done now! Waiting for you to complete the tutorial page to have the basics done. |
@saranshkataria Awesome. |
I can take a crack at the |
Cool. go ahead. Which warning page you will be working on? Can you pick one, so I can assign your name next to page name |
I can start with |
Cool. I will add your username to that page. |
Just curious if there is any long term automation plan to keep the docs in sync with the English version? Or the updates are expected to happen manually every time? |
Can I translate the Styling and CSS page? |
@PriyankaCodes99 go for it! Adding your name next to it |
Thanks! The work is in progress. |
Hey, Can I translate Rendering Elements page? |
@AbhishekCode go ahead. I will assign your name next to the page |
@arshadkazmi42 Thanks 👍 |
@arshadkazmi42 Can I translate the react section under API REFERENCE. |
@Hrshk15 Assigned API Reference > React page to you. This is the page you need to translate Translate the complete file in Hindi. Refer #2 for common translations. For creating branch locally follow this |
I have tried running it locally, following the steps mentioned. ERROR #85923 GRAPHQL There was an error in your GraphQL query: Cannot query field "allExampleCode" on type "Query". Kindly suggest me what should I do. |
Follow the below steps
if you are seeing some error after this, share screenshot and error logs. |
Hi @arshadkazmi42 |
@neeraj-here assigned 👍 |
After
**HP@LAPTOP-BNE4L5IB MINGW64 ~ HP@LAPTOP-BNE4L5IB MINGW64 /e
yarn run v1.22.5 Error: Cannot use GraphQLInputObjectType "FileInput" from another module or realm. Ensure that there is only one instance of "graphql" in the node_modules https://yarnpkg.com/en/docs/selective-version-resolutions Duplicate "graphql" modules cannot be used at the same time since different success open and validate gatsby-configs - 0.188s ERROR Missing onError handler for invocation 'building-schema', error was 'TypeError: (0 , _graphql.isScalarType) is not a function'. Stacktrace was 'TypeError: (0 , _graphql.isScalarType) is not a function ⠴ building schema** It seems to be indefinite as nothing happens after this. |
@neeraj-here do you have access to GitHub codespaces beta? If not then check this blog, and open the project in code sandbox instead. Maybe this might help. |
@saranshkataria @arshadkazmi42 |
Hi, Can I take dont-call-proptypes page for translation ? |
try delete node-modules folder and package-lock.json or yarn.lock then try running |
sure @tanishqchamola . page assigned |
@ShivamPorwal02 page assigned |
Can I also help in translation of reactjs? |
Hi, can I help with translating the |
I would like to work upon the issue #26 and translate "State and Lifecycle". |
Hi @arshadkazmi42, can I help with translating the Reconciliation page? |
@tesseralis I would like to translate React Without JSX page in Advanced Guides. |
@vishalnagda1 Go ahead |
@arshadkazmi42 Completed the last task. Please review the PR #163 |
@arshadkazmi42 Should I proceed with JSX In Depth page in Advanced Guides for translation, or should I wait for previous PR to get merge before starting with new one? |
@vishalnagda1 sure go ahead |
Thanks to everyone who contributed to this iteration! |
Translation details of beta site is available here #168
We are not translating these pages anymore.
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 find that you can't commit any more, 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!
Core Pages
To do before releasing as an "official" translation. Please translate these pages first.
Basics
API Reference
Navigation
These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.
Next Steps
These are the next most important translations, ordered by importance:
Installation
Hooks
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.
Warnings
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.
Advanced Guides
FAQ
Contributing
Priority: Low
Components
Components in
src/components
that have some text in them.Additional Translations
These are not the primary translation targets.
The text was updated successfully, but these errors were encountered: