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

Style Guide #22

Open
itayyehezkel opened this issue Feb 26, 2019 · 19 comments
Open

Style Guide #22

itayyehezkel opened this issue Feb 26, 2019 · 19 comments

Comments

@itayyehezkel
Copy link
Collaborator

itayyehezkel commented Feb 26, 2019

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 ממשק משתמש
@galnir
Copy link
Collaborator

galnir commented Feb 26, 2019

Yeah it's a great idea
Btw all the translations we pushed so far refer to 'component' as קומפוננטה and 'React' as ריאקט

@galtalmor
Copy link
Collaborator

galtalmor commented Feb 26, 2019

Good initiative!
Some thoughts:

  1. Should we actually translate React to ריאקט or leave it in English? I think leaving it in English is more appropriate.
  2. Also, I just stumbled upon @yarons' suggestion to translate repository to מאגר, which I disagree with, thinking a clearer translation would be ריפוזיטורי.
  3. Shouldn't we translate UI to ממשק משתמש as well, I think we should?
  4. 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.
  5. Why not translate cleanup to נקיון/לנקות? Same as above.
  6. Why not translate lifecycle to מחזור חיים? Same as above.
  7. Lastly, we need to decide in which noun we use, should we translate "you" as את\ה or אתם? I vote for אתם.
  8. 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?

@itayyehezkel
Copy link
Collaborator Author

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.

@yarons
Copy link

yarons commented Feb 27, 2019

There are solutions to avoid את/ה/ם, it requires making the text less personal and more generalized so it will approach to women as well.

@galtalmor
Copy link
Collaborator

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

@yarons
Copy link

yarons commented Feb 27, 2019

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

@galnir
Copy link
Collaborator

galnir commented Feb 27, 2019

@yarons I agree with @galtalmor, if we want to avoid את/ה the only option is אתם(which I used in 'thinking in react' translation)

@yarons
Copy link

yarons commented Feb 27, 2019

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

@itayyehezkel
Copy link
Collaborator Author

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.

@yarons
Copy link

yarons commented Feb 27, 2019

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

@galtalmor
Copy link
Collaborator

galtalmor commented Feb 27, 2019

Okay lets do it this way (please only vote once):



@dormd
Copy link
Contributor

dormd commented Feb 28, 2019

production - production

@dormd
Copy link
Contributor

dormd commented Feb 28, 2019

What do you think?
Attribute - תכונה
HTTP header - HTTP header

@galtalmor
Copy link
Collaborator

galtalmor commented Feb 28, 2019

I think Attribute should be מאפיין to distinguish it from "feature".
I agree about HTTP header.

@itayyehezkel
Copy link
Collaborator Author

Great! Please join to Slack Hebrew channel which can we talk about it in depth.

@beniregev
Copy link

beniregev commented Sep 23, 2019

I suggest the followings:

bind קשירה
context תוכן
constructor קונסטרקטור
markup סימון
method מתודה/שיטה
mount מאונט
production סביבת ייצור
props פרופס
React ריאקט
reconciliation הסתרה מחדש
ref ref
UX חוויית משתמש
user experience חוויית משתמש

@Sa-ar
Copy link

Sa-ar commented May 25, 2023

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)

@galnir
Copy link
Collaborator

galnir commented May 25, 2023

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

@beniregev
Copy link

beniregev commented May 26, 2023

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.

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

No branches or pull requests

7 participants