Skip to content
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

Closed
17 of 88 tasks
tesseralis opened this issue Feb 10, 2019 · 175 comments
Closed
17 of 88 tasks

[OLD] Legacy Hindi Translation Progress #1

tesseralis opened this issue Feb 10, 2019 · 175 comments
Labels

Comments

@tesseralis
Copy link
Member

tesseralis commented Feb 10, 2019

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:

  1. Check that no one else has claimed your page in the checklist and comments below.
  2. Comment below with the name of the page you would like to translate. Please take only one page at a time.
  3. Clone this repo, translate your page, and submit a pull request!

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.

  • tutorial/nav.yml
  • docs/nav.yml

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.

  • dont-call-proptypes (@ShivamPorwal02 )
  • invalid-aria-prop
  • invalid-hook-call-warning
  • legacy-factories
  • refs-must-have-owner
  • special-props
  • unknown-prop

Advanced Guides

  • Accessibility
  • Code-Splitting
  • Context
  • Error Boundaries
  • Forwarding Refs
  • Fragments
  • Higher-Order Components
  • Integrating with Other Libraries
  • JSX In Depth (@vishalnagda1 )
  • Optimizing Performance
  • Portals (@Mayankverr ) portals page #73
  • React Without ES6 (@kumari1224 )
  • React Without JSX (@vishalnagda1)
  • Reconciliation
  • Refs and the DOM
  • Render Props
  • Static Type Checking
  • Strict Mode
  • Typechecking With PropTypes
  • Uncontrolled Components
  • Web Components

FAQ

Contributing

Priority: Low

  • How to Contribute
  • Codebase Overview
  • Implementation Notes
  • Design Principles

Components

Components in src/components that have some text in them.

  • CodeEditor
  • CodeExample
  • ErrorDecoder
  • LayoutFooter
  • LayoutHeader
  • MarkdownPage

Additional Translations

These are not the primary translation targets.

  • Blog
  • Community
@arshadkazmi42
Copy link
Member

@saranshkataria I am starting with Tutrial page

@apoorvtomar2222
Copy link
Contributor

apoorvtomar2222 commented Feb 10, 2019

@tesseralis @arshadkazmi42 @saranshkataria

How can we differentiate that what all pages among the list have already been done ?

@arshadkazmi42
Copy link
Member

arshadkazmi42 commented Feb 10, 2019

@apoorvtomar2222 If any page is completed, it will has a check mark like below

  • Done
    And if its in progress it will have the username of contributor who is working on it like below
  • Page (@arshadkazmi42 )

@arshadkazmi42
Copy link
Member

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.

@saranshkataria
Copy link
Member

@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.

@saranshkataria saranshkataria pinned this issue Feb 10, 2019
@gurjotsingh4398
Copy link
Contributor

I would like to work on Hello World page.

@arshadkazmi42
Copy link
Member

Go ahead

@arshadkazmi42
Copy link
Member

@saranshkataria Home Page is still not completely translated. I have unmarked it as done.
You can try running it locally. These are the subtitles which are not translated.

  • A Simple Component
  • A Stateful Component
  • An Application
  • A Component Using External Plugins

We will mark it as done, when all these are also translated.

@saranshkataria
Copy link
Member

@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.

@arshadkazmi42
Copy link
Member

arshadkazmi42 commented Feb 12, 2019

Ok cool. I thought you missed it.
I think those are part of Home page right? Or do we have separate entries for those in the list?

We will add tick mark to every item once its {{done done}}

@saranshkataria
Copy link
Member

They are in the home page. Also, should we split these into multiple issues instead of just one?

@arshadkazmi42
Copy link
Member

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

@saranshkataria
Copy link
Member

@arshadkazmi42 the home page is done now! Waiting for you to complete the tutorial page to have the basics done.

@arshadkazmi42
Copy link
Member

@saranshkataria Awesome.
I am 70% done with the tutorial page. Will send a PR in a day or two

@hozefaj
Copy link
Contributor

hozefaj commented Feb 17, 2019

I can take a crack at the Warning section.

@arshadkazmi42
Copy link
Member

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

@hozefaj
Copy link
Contributor

hozefaj commented Feb 17, 2019

I can start with dont-call-proptypes. Do you have a timeline by which the pages need to get done?

@arshadkazmi42
Copy link
Member

Cool. I will add your username to that page.
We don't have any fixed timelines, but if you get stuck at anything you can let us know.

@hozefaj
Copy link
Contributor

hozefaj commented Feb 17, 2019

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?

@tesseralis
Copy link
Member Author

@hozefaj a bot will create PRs around once a day when it detects changes to master branch, as so:

#11

@PriyankaCodes99
Copy link

Can I translate the Styling and CSS page?

@saranshkataria
Copy link
Member

@PriyankaCodes99 go for it! Adding your name next to it

@PriyankaCodes99
Copy link

PriyankaCodes99 commented Feb 20, 2019

@PriyankaCodes99 go for it! Adding your name next to it

Thanks! The work is in progress.

@AbhishekCode
Copy link

Hey, Can I translate Rendering Elements page?

@arshadkazmi42
Copy link
Member

@AbhishekCode go ahead. I will assign your name next to the page

@AbhishekCode
Copy link

@arshadkazmi42 Thanks 👍

@Hrshk15
Copy link

Hrshk15 commented Sep 3, 2020

@arshadkazmi42 Can I translate the react section under API REFERENCE.
And if yes , thn can u kindly tell me the procedure.

@arshadkazmi42
Copy link
Member

@Hrshk15 Assigned API Reference > React page to you.

This is the page you need to translate
https://github.com/reactjs/hi.reactjs.org/blob/master/content/docs/reference-react.md

Translate the complete file in Hindi. Refer #2 for common translations.
Do not translate code blocks.
Once complete file is translated, send a PR for review.
There will be two phases of review. Once your PR gets approved from both the reviewers, your change will be merged.

For creating branch locally follow this
https://github.com/reactjs/hi.reactjs.org#create-a-branch

@Hrshk15
Copy link

Hrshk15 commented Sep 6, 2020

I have tried running it locally, following the steps mentioned.
But it gives this error-

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.

@arshadkazmi42
Copy link
Member

Follow the below steps

  1. Clone repository
  2. Run npm install in the root directory hi.reactjs.org
  3. Run npm start

if you are seeing some error after this, share screenshot and error logs.

@neeraj-here
Copy link

Hi @arshadkazmi42
I am interested in translating the ReactDOMServer under API Reference. Can I do that? If yes, please guide me with the procedure.

@saranshkataria
Copy link
Member

@neeraj-here assigned 👍

@neeraj-here
Copy link

@neeraj-here assigned 👍

After

Follow the below steps

  1. Clone repository
  2. Run npm install in the root directory hi.reactjs.org
  3. Run npm start

if you are seeing some error after this, share screenshot and error logs.
@arshadkazmi42 @saranshkataria
I faced the same problem as by @Hrshk15 . Tried the above mentioned way but still getting a error. Here are the logs:

**HP@LAPTOP-BNE4L5IB MINGW64 ~
$ cd e:
HP@LAPTOP-BNE4L5IB MINGW64 /e
$ dir
!qhlogs.doc CodeBlocks GIMP\ 2 My\ photos System\ Volume\ Information
$RECYCLE.BIN coursera-sub Interactivity\ with\ JS New\ folder website
bootstrap DS It's\ me.rtf New\ folder\ (2) Whatsapp\ docs
cfrbackup-SSNIWRZC DS.c movies reactjs.org

HP@LAPTOP-BNE4L5IB MINGW64 /e
$ cd reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org
$ cd hi.reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org/hi.reactjs.org (master)
$ npm start

react-website@0.0.1 start E:\reactjs.org\hi.reactjs.org
yarn dev

yarn run v1.22.5
$ gatsby develop -H 0.0.0.0
E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28
throw new Error("Cannot use ".concat(className, " "").concat(value, "" from another module or realm.\n\nEnsure that there is only one instance of "graphql" in the node_modules\ndirectory. If different versions of "graphql" are the dependencies of other\nrelied on modules, use "resolutions" to ensure only one version is installed.\n\nhttps://yarnpkg.com/en/docs/selective-version-resolutions\n\nDuplicate "graphql" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results."));
^

Error: Cannot use GraphQLInputObjectType "FileInput" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.
at instanceOf (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28:13)
at isInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\definition.js:168:34)
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:290:41)
at Array.reduce ()
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:285:34)
at Array.reduce ()
at new GraphQLSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:145:28)
at Object. (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\dist\graphql-server\server.js:223:16)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)

success open and validate gatsby-configs - 0.188s
success load plugins - 4.133s
success onPreInit - 0.190s
success initialize cache - 0.045s
success copy gatsby files - 0.234s
warn gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
This means that the plugin will use the default feed title, which may not match your use case.
This behavior will be removed in the next major release of gatsby-plugin-feed.
For more info, check out: https://gatsby.dev/adding-rss-feed
success onPreBootstrap - 0.049s
success createSchemaCustomization - 0.407s
success Checking for changed pages - 0.006s
success source and transform nodes - 8.971s

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
at TypeMapper.get (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:88:76)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:608:17)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:603:24)
at TypeMapper.getWrapped (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:105:17)
at TypeMapper.convertOutputFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:272:114)
at resolveOutputConfigAsThunk (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\configAsThunk.js:19:41)
at ObjectTypeComposer.getFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:300:58)
at E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:44:19
at Array.forEach ()
at toInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:38:14)
at ObjectTypeComposer.getInputTypeComposer (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:600:84)
at E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:22:8
at SchemaComposer.getOrCreateOTC (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\SchemaComposer.js:382:54)
at getOrCreateNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:10:37)
at getNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:81:3)
at createSchemaComposer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\schema-composer.js:15:3)
at build (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\index.js:104:26)
at buildSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\services\build-schema.ts:19:3)'

⠴ building schema**

It seems to be indefinite as nothing happens after this.
Please guide me the solution or any alternative.

@bhatvikrant
Copy link

@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.

@tanishqchamola
Copy link

@saranshkataria @arshadkazmi42
Hi, can I help with translating Test Renderer page?

@ShivamPorwal02
Copy link

Hi, Can I take dont-call-proptypes page for translation ?

@arshadkazmi42
Copy link
Member

@neeraj-here assigned 👍

After

Follow the below steps

  1. Clone repository
  2. Run npm install in the root directory hi.reactjs.org
  3. Run npm start

if you are seeing some error after this, share screenshot and error logs.
@arshadkazmi42 @saranshkataria
I faced the same problem as by @Hrshk15 . Tried the above mentioned way but still getting a error. Here are the logs:

**HP@LAPTOP-BNE4L5IB MINGW64 ~
$ cd e:
HP@LAPTOP-BNE4L5IB MINGW64 /e
$ dir
!qhlogs.doc CodeBlocks GIMP\ 2 My\ photos System\ Volume\ Information
$RECYCLE.BIN coursera-sub Interactivity\ with\ JS New\ folder website
bootstrap DS It's\ me.rtf New\ folder\ (2) Whatsapp\ docs
cfrbackup-SSNIWRZC DS.c movies reactjs.org

HP@LAPTOP-BNE4L5IB MINGW64 /e
$ cd reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org
$ cd hi.reactjs.org
HP@LAPTOP-BNE4L5IB MINGW64 /e/reactjs.org/hi.reactjs.org (master)
$ npm start

react-website@0.0.1 start E:\reactjs.org\hi.reactjs.org
yarn dev

yarn run v1.22.5
$ gatsby develop -H 0.0.0.0
E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28
throw new Error("Cannot use ".concat(className, " "").concat(value, "" from another module or realm.\n\nEnsure that there is only one instance of "graphql" in the node_modules\ndirectory. If different versions of "graphql" are the dependencies of other\nrelied on modules, use "resolutions" to ensure only one version is installed.\n\nhttps://yarnpkg.com/en/docs/selective-version-resolutions\n\nDuplicate "graphql" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results."));
^

Error: Cannot use GraphQLInputObjectType "FileInput" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.
at instanceOf (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\jsutils\instanceOf.js:28:13)
at isInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\definition.js:168:34)
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:290:41)
at Array.reduce ()
at typeMapReducer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:285:34)
at Array.reduce ()
at new GraphQLSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\node_modules\graphql\type\schema.js:145:28)
at Object. (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby-recipes\dist\graphql-server\server.js:223:16)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)

success open and validate gatsby-configs - 0.188s
success load plugins - 4.133s
success onPreInit - 0.190s
success initialize cache - 0.045s
success copy gatsby files - 0.234s
warn gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
This means that the plugin will use the default feed title, which may not match your use case.
This behavior will be removed in the next major release of gatsby-plugin-feed.
For more info, check out: https://gatsby.dev/adding-rss-feed
success onPreBootstrap - 0.049s
success createSchemaCustomization - 0.407s
success Checking for changed pages - 0.006s
success source and transform nodes - 8.971s

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
at TypeMapper.get (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:88:76)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:608:17)
at TypeMapper.typeFromAST (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:603:24)
at TypeMapper.getWrapped (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:105:17)
at TypeMapper.convertOutputFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\TypeMapper.js:272:114)
at resolveOutputConfigAsThunk (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\configAsThunk.js:19:41)
at ObjectTypeComposer.getFieldConfig (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:300:58)
at E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:44:19
at Array.forEach ()
at toInputObjectType (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\utils\toInputObjectType.js:38:14)
at ObjectTypeComposer.getInputTypeComposer (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\ObjectTypeComposer.js:600:84)
at E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:22:8
at SchemaComposer.getOrCreateOTC (E:\reactjs.org\hi.reactjs.org\node_modules\graphql-compose\lib\SchemaComposer.js:382:54)
at getOrCreateNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:10:37)
at getNodeInterface (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\types\node-interface.js:81:3)
at createSchemaComposer (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\schema-composer.js:15:3)
at build (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\schema\index.js:104:26)
at buildSchema (E:\reactjs.org\hi.reactjs.org\node_modules\gatsby\src\services\build-schema.ts:19:3)'

⠴ building schema**

It seems to be indefinite as nothing happens after this.
Please guide me the solution or any alternative.

try delete node-modules folder and package-lock.json or yarn.lock then try running yarn and then yarn dev

@arshadkazmi42
Copy link
Member

@saranshkataria @arshadkazmi42
Hi, can I help with translating Test Renderer page?

sure @tanishqchamola . page assigned

@arshadkazmi42
Copy link
Member

Hi, Can I take dont-call-proptypes page for translation ?

@ShivamPorwal02 page assigned

@vivek80801
Copy link

Can I also help in translation of reactjs?

@vieee
Copy link

vieee commented Nov 2, 2020

Hi, can I help with translating the Hooks API reference page within the Hooks section..?

@piyush9311
Copy link

I would like to work upon the issue #26 and translate "State and Lifecycle".

@Himnashu
Copy link

Hi @arshadkazmi42, can I help with translating the Reconciliation page?

@vishalnagda1
Copy link

@tesseralis I would like to translate React Without JSX page in Advanced Guides.
Please assign it to me.

@arshadkazmi42
Copy link
Member

@tesseralis I would like to translate React Without JSX page in Advanced Guides.

Please assign it to me.

@vishalnagda1 Go ahead

@vishalnagda1
Copy link

@arshadkazmi42 Completed the last task. Please review the PR #163
Next I would like to take JSX In Depth page in Advanced Guides for translation.

@vishalnagda1
Copy link

@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?

@arshadkazmi42
Copy link
Member

@vishalnagda1 sure go ahead

@reactjs reactjs locked as resolved and limited conversation to collaborators Dec 9, 2021
@arshadkazmi42 arshadkazmi42 unpinned this issue Dec 9, 2021
@arshadkazmi42 arshadkazmi42 added Locked and removed help wanted Extra attention is needed labels Dec 9, 2021
@gaearon
Copy link
Member

gaearon commented Apr 25, 2023

Thanks to everyone who contributed to this iteration!
Here is the issue for the new website translation: #168.

@gaearon gaearon closed this as completed Apr 25, 2023
@gaearon gaearon changed the title Hindi Translation Progress [OLD] Legacy Hindi Translation Progress Apr 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests