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

Fix component transliteration #19

Closed
wants to merge 1 commit into from
Closed

Fix component transliteration #19

wants to merge 1 commit into from

Conversation

siddharthkp
Copy link
Contributor

@siddharthkp siddharthkp commented Feb 27, 2019

Hi!

I think the right transliteration of component is:

- कौम्पोनॅन्ट
+ कॉम्पोनेन्ट

because it's not komponent, it's kaumponent? the pronunciation might help convey what I'm trying to say.


  1. Confirmed with Google input tools

  2. Google translate agrees:

screenshot 2019-02-27 at 11 00 51 am

(I don't know if we can trust transliteration tools though, it's always subjective?)


This is pretty much in every page

cc: @saranshkataria @arshadkazmi42 @tesseralis

@netlify
Copy link

netlify bot commented Feb 27, 2019

Deploy preview for hi-reactjs ready!

Built with commit a6de2e6

https://deploy-preview-19--hi-reactjs.netlify.com

Copy link

@reeversedev reeversedev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds more familiar in Hindi.

@siddharthkp siddharthkp mentioned this pull request Feb 27, 2019
@kashishgrover
Copy link

मज़े ले रहे हो यार तुम तो

@arshadkazmi42
Copy link
Member

My personal opinion on this is, using any of these are fine, it just needs to convey the correct meaning as we not translating it.
Just writing the pronunciation in hindi can be in different spelling as many people pronounce same words differently.
@saranshkataria Can you have a look at this!

@siddharthkp
Copy link
Contributor Author

@arshadkazmi42 💯 I totally agree with you, please don't spend too much time on this

There's some value in correctness while doing translation/transliteration, but you it's pretty tiny at this stage of the project

@arshadkazmi42
Copy link
Member

@arshadkazmi42 100 I totally agree with you, please don't spend too much time on this

There's some value in correctness while doing translation/transliteration, but you it's pretty tiny at this stage of the project

I think we can close this PR for now.
Also if you would like to contribute to this repo, we have alot of pages pending to be translated you can pick 1 from #1

@saranshkataria
Copy link
Member

I think either of them is fine and we can just move ahead with what we have decided. Getting into such semantics and discussions will only increase the debate and such arguments won't be of much help especially when they are just slightly off. Closing this out. Hope you can help in translating other pages 😄

@tesseralis
Copy link
Member

As long as you choose one, put it in the glossary, and stick with it. Also, if you decide to change the spelling later, is should be easy to do a find-replace for the word, right?

@arshadkazmi42
Copy link
Member

💯

@saranshkataria
Copy link
Member

As long as you choose one, put it in the glossary, and stick with it. Also, if you decide to change the spelling later, is should be easy to do a find-replace for the word, right?

it already was in the glossary. So we are good there.

@paramaggarwal
Copy link
Contributor

paramaggarwal commented Aug 23, 2019

Please go with कॉम्पोनेन्ट. The pronunciation of कौम्पोनॅन्ट is completely off.

कॉम्पोनेन्ट - KOMPONENT
कौम्पोनॅन्ट - KOUMPONONT

I request this be re-opened.

@arshadkazmi42
Copy link
Member

@paramaggarwal We have already discussed about this. For now we are keeping it कौम्पोनॅन्ट and later if we plan to change it, it will be just find and replace all.
Right now, priority for us is to get everything translated, later we can work on fixing these types of small things.

@paramaggarwal
Copy link
Contributor

Right now, priority for us is to get everything translated

Yeah, makes sense!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants