he.react.dev
he.react.dev copied to clipboard
reactjs
Style Guide
Hey guys,
I think we should stay synchronized by adding a style guide as @tesseralis mentioned in her issue. So I made a few translations which makes sense for me, but feel free to suggest something else. After we all agree about the common language I'll create TRANSLATION.md file.
Style Guide
| Original | Translation |
|---|---|
| application | אפליקציה |
| array | מערך |
| attribute | מאפיין |
| bind | bind |
| callback | callback |
| class | מחלקה |
| cleanup | נקיון\לנקות |
| component | קומפוננטה |
| context | context |
| constructor | בנאי |
| DOM | DOM |
| element | אלמנט |
| encapsulated | מכומס |
| export | ייצוא |
| feature | תכונה |
| function | פונקציה |
| Hook | Hook |
| HTTP header | HTTP header |
| import | ייבוא |
| key | מפתח |
| library | ספרייה |
| lifecycle | מחזור חיים |
| markup | markup |
| method | מתודה |
| module | מודול |
| mount | mount |
| node | צומת |
| object | אובייקט |
| production | production |
| props | props |
| React | React |
| reconciliation | reconciliation |
| ref | ref |
| render | רנדר\לרנדר |
| repository | ריפוזיטורי |
| section | חלק |
| state | state |
| string | מחרוזת |
| TLDR | אמ;לק |
| UI | ממשק משתמש |
| user interface | ממשק משתמש |
Yeah it's a great idea Btw all the translations we pushed so far refer to 'component' as קומפוננטה and 'React' as ריאקט
Good initiative! Some thoughts:
- Should we actually translate React to ריאקט or leave it in English? I think leaving it in English is more appropriate.
- Also, I just stumbled upon @yarons' suggestion to translate repository to מאגר, which I disagree with, thinking a clearer translation would be ריפוזיטורי.
- Shouldn't we translate UI to ממשק משתמש as well, I think we should?
- Why not translate key to מפתח? In my opinion, when there's a good Hebrew translation for a word it should be translated, in order to help those with weaker English, except if it is a core keyword in React like state for example.
- Why not translate cleanup to נקיון/לנקות? Same as above.
- Why not translate lifecycle to מחזור חיים? Same as above.
- Lastly, we need to decide in which noun we use, should we translate "you" as את\ה or אתם? I vote for אתם.
- I would add to the list: section -> חלק, render -> לרנדר, encapsulated -> מכומס\ת, method -> מתודה, DOM node -> צומת DOM?, application -> אפליקצייה, mounting -> mounting?, constructor -> בנאי
What do you guys think of these issues?
Thanks @galtalmor I tend to agree with you, I think that we should listen to our readers, most of Israeli FED industry using English terms and we should not translate every term to Hebrew. And את\ה sounds to me more personal, but I would like to see what others think about it.
There are solutions to avoid את/ה/ם, it requires making the text less personal and more generalized so it will approach to women as well.
@yarons I don't think avoidance is a good solution, it will require the translation to be different from the original, make it harder to translate and as you said will be less personal. I think that choosing either אתה or אתם will be the best solution, we just need to choose one and stick with it. IMO אתם is the better option since it is kind of directed to both sexes, while אתה isn't, but that's only my opinion.
@galtalmor The translations of Firefox, Wikipedia, Ubuntu, VLC, Mac OS X etc. are all using these rules so it's pretty common to avoid gender (Facebook for example is using dynamic gender customization system so the messages are gender related and usually does not require any additional conjugation).
אתה is the default gender in Hebrew, applies also to women but it's less natural to them so I tend to avoid it. אתם just doesn't sound right and pretty claustrophobic (who else is with me?).
Do as you wish, I'm just sharing some insights from my personal history, I can only recommend.
@yarons I agree with @galtalmor, if we want to avoid את/ה the only option is אתם(which I used in 'thinking in react' translation)
@galnir As you wish, as I was saying, most well-known open source solutions are translated without gender bias, there's absolutely no reason to use plural form.
What do you think about check with other groups to see how they solved it? maybe all languages with grammatical genders should do the same.
@itayyehezkel It's more relevant when you ask yourself whether to translate, transliterate or keep the term as it is, it's less relevant to gender issues, French and Russian for example has a third gender (neutral) so they don't have this problem, In Arabic it's pretty common to use the masculine form (Even love songs that are targeted at women, sang be men, are in masculine form).
Cultural diversity does not really allow having all these comparisons since they don't make any sense.
I think Attribute should be מאפיין to distinguish it from "feature". I agree about HTTP header.
I suggest the followings:
bind קשירה context תוכן constructor קונסטרקטור markup סימון method מתודה/שיטה mount מאונט production סביבת ייצור props פרופס React ריאקט reconciliation הסתרה מחדש ref ref UX חוויית משתמש user experience חוויית משתמש
A few things I stumbled upon in my translation that I'm not sure how to translate:
- Framework
- Deploy
- Serverless
- Adapter (in context of Remix adapter)
A few things I stumbled upon in my translation that I'm not sure how to translate:
In my opinion, these words shouldn't be translated because they are commonly used as-is in the Hebrew speaking tech community
I mainly agree with @galnir , We don't translate "Framework" just write it in Hebrew letters, and the same for "Serverless". However, Adapter is usually translated "מתאם" in Hebrew, and Deploy is "הפצה". Framework = פריימוורק Deploy = הפצה Serverless = סרברלס or ללא-שרת if you insist on translating it, but it makes it less understandable. Adapter (in the context of Remix adapter) = מתאם or in the meaning of a design pattern do not translate it. By the way, I'm also against translating words such as "Cookie" to "עוגייה" - it's just inaccurate and confusing.