Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Glossary #6

Open
3sanket3 opened this issue Mar 13, 2019 · 28 comments
Open

Glossary #6

3sanket3 opened this issue Mar 13, 2019 · 28 comments

Comments

@3sanket3
Copy link
Contributor

3sanket3 commented Mar 13, 2019

The words that should be transliterated.

Whose English pronunciation are generally familiar to Gujarati reader

Words Transliteration
Application એપ્લિકેશન
method મેથડ
implement ઈમ્પ્લીમેન્ટ
interface ઇન્ટરફેસ
tutorial ટ્યૂટોરિઅલ
value વેલ્યુ
painless પેઇનલેસ
invoke ઈન્વોક
Rendering રેન્ડરિંગ
Page પેજ

The words needs to be kept as it is:

Programming Jargons

Words
Elements
Component(s)
server
technology stack
Node
render
Encapsulated
state
UI
logic
templates
JavaScript
libraries
frameworks
Plugins
Stateful
User
Polyfill
shim

The words needs to be translated:

Words Transliteration
Docs માર્ગદર્શિકા
@3sanket3
Copy link
Contributor Author

From my perspective and initial thoughts. I would love to hear your suggestions to improve the same.

@3sanket3
Copy link
Contributor Author

Instead of "કેમ છો?"

Hello world should be "નમસ્તે "
by @Str1kemeister

I think "કેમ છો?" gives a more Gujarati touch. isn't નમસ્તે a kind of a Hindi word?

@jayPatel222
Copy link

Namastey may sounds like a hindi word but I think most appropriate way to say hello.
Google translate is also aiming at namastay for hello in Gujarati

@ron4ex
Copy link
Contributor

ron4ex commented Mar 14, 2019

If we go for literal translation of Hello then you're right @Str1kemeister, નમસ્તે is better. However the iconic phrase of "Hello world" has been used as a form of greeting since the beginning. So in terms of greetings, I don't think there's a more iconic phrase than કેમ છો in Gujarati. Perhaps we can take a bit of liberty in this case and not go for the literal translation. Should we add દુનિયા at the end?

@sonipreshita
Copy link
Contributor

sonipreshita commented Mar 14, 2019

Aren't we keep "Hello world" as it is? And it also makes sense and understandable. "કેમ છો?" is not the exact translation in Gujarati. If we keep "નમસ્તે દુનિયા" then it sounds little weird. Or you guys can give any suggestion which will be feasible instead of this sentence.

@ron4ex
Copy link
Contributor

ron4ex commented Mar 14, 2019

We've explored many other translations (either finished or in progress) and they are going for a native phrase of their language. You can check them out at https://reactjs.org/languages

Harmless strings that are meant just for the purpose of examples can be native and in my opinion should be native. Think about it this way - Translation of Hello World is an opportunity to add a Gujarati flavor to the documentation. It is relatable to the readers and keeps them excited. 😃

@3sanket3
Copy link
Contributor Author

Added Rendering -> રેન્ડરિંગ

@3sanket3
Copy link
Contributor Author

@Str1kemeister @ron4ex @sonipreshita

We will have to keep 'Hello World' as it is. At many places in documentation, the code from .js file is directly pulled for code snippets in doc. And if the code in .js file tries to print 'Hello World', we will have update the .js file from src folder. Which we think out of translation scope. We may have to update the same in other translated pages as well.

Thanks all for your inputs. I have updated the Glossary accordingly.

@3sanket3
Copy link
Contributor Author

Any suggestions for the translation of 'immutable'?

Going with અપરિવર્તીત for now. I would love to hear your suggestions.

@jayPatel222
Copy link

tutorial | ટ્યૂટોરિઅલ
i think it would be great if it was "Namuno" and for "immutable" ,"satat" is also good option.

@cristatus
Copy link

Any suggestions for the translation of 'immutable'?

Going with અપરિવર્તીત for now. I would love to hear your suggestions.

અપરિવર્તીત is more like unchanged. I think better word is "અચળ" or "અવિચલ". You can refer http://www.bhagvadgomandal.com/ when any doubts.

@ron4ex
Copy link
Contributor

ron4ex commented Apr 4, 2019

અચળ or સતત are literal translations of the word constant which would be conflicting when we'll need to translate the word constant. I think અપરિવર્તીત can be uniquely associated with the word immutable.

@ron4ex ron4ex mentioned this issue Apr 20, 2019
88 tasks
@amincharoliya
Copy link

Any suggestions for the word "assert".
The sentence is: "assert facts about what its render method returns".

@ron4ex
Copy link
Contributor

ron4ex commented May 18, 2019

I think the phrase that you've mentioned uses the word assert in reference to testing. And in testing, assert points to confirming or verifying but in a more intense manner I guess. So something along the lines of ખાતરીપૂર્વક ચકાસો might be the closest translation of it.

@3sanket3
Copy link
Contributor Author

React also depends on requestAnimationFrame (even in test environments).
You can use the raf package to shim requestAnimationFrame:

Any input on, what does shim means in above paragraph?

cc: @ron4ex

@ron4ex
Copy link
Contributor

ron4ex commented May 22, 2019

shim is word used for a wrapper of any sorts. For example, an older browser that doesn't support fetch natively may require a shim. polyfill is a type os shim.

I think we should consider both of those words as JavaScript jargon and use them as they are.

@3sanket3
Copy link
Contributor Author

Ok, make sense. We will use them as it is(in English itself). Updated the issue body.

@kamal250
Copy link

Mock should be મૉક.

@amincharoliya
Copy link

I think the phrase that you've mentioned uses the word assert in reference to testing. And in testing, assert points to confirming or verifying but in a more intense manner I guess. So something along the lines of ખાતરીપૂર્વક ચકાસો might be the closest translation of it.

@ron4ex You are right. But after reading the whole paragraph "assert" meaning "ખાતરીપૂર્વક ચકાસો" doesn't fit well. Check the below paragraph:

When writing unit tests for React, shallow rendering can be helpful. Shallow rendering lets you render a component “one level deep” and assert facts about what its render method returns, without worrying about the behavior of child components, which are not instantiated or rendered. This does not require a DOM."

@ron4ex
Copy link
Contributor

ron4ex commented May 22, 2019

I think in this case, it's more about showing the intent rather than testing-related assert. It's not necessary to go for literal translation when there isn't a straight forward one. The intent here is clearly about how much confidence shallow rendering can give the user.

How about translating for ...and gives you confidence about what its render method returns...

@vsgheravada
Copy link

Any suggestions for the translation of 'immutable'?

Going with અપરિવર્તીત for now. I would love to hear your suggestions.

અપરિવર્તીત is more like unchanged. I think better word is "અચળ" or "અવિચલ". You can refer http://www.bhagvadgomandal.com/ when any doubts.

I agree with you. "અચળ" will be more familiar & understandable.

@harshilparmar
Copy link

@3sanket3 I am working on the hooks introduction page, is "hook" should be translated or not?

@ron4ex
Copy link
Contributor

ron4ex commented Aug 13, 2020

@harshilparmar Yeah I think hooks translation is assigned to you as per #1. The translation progress has been stalled a bit. It would be great if you can put in any page. Please don't be hesitant to create a PR and submit.

@harshilparmar
Copy link

@ron4ex Thanks brother..I want to ask that is "hook" word going to as it is or it should be translated in gujarati ? like "હૂક"?

@ron4ex
Copy link
Contributor

ron4ex commented Aug 13, 2020

Oh okay. I misunderstood your original comment. It should be transilerated to "હૂક". The general rule is, if the pure gujarati translation doesn't make sense, just transilerate as indicated by some of the examples in issue description.

@PhoenixCreation
Copy link
Contributor

What about react? Should it be translated to રીએક્ટ ? or should I keep it 'react'?

@ron4ex
Copy link
Contributor

ron4ex commented Oct 14, 2020

Keep react in English.

@PhoenixCreation
Copy link
Contributor

ok...Thanks

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

No branches or pull requests

10 participants