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

Name Glossary #10

Open
ph1p opened this issue Feb 11, 2019 · 16 comments
Open

Name Glossary #10

ph1p opened this issue Feb 11, 2019 · 16 comments
Assignees

Comments

@ph1p
Copy link
Member

ph1p commented Feb 11, 2019

This glossary is intended for frequently used words.

English German Depends on context
Note Hinweis -
Tip Tipp -
shim ? x
polyfill Polyfill -
state State x
templates ? -
Setup Setup -
immutability -
immutable immutable -
Properties Properties or Eigenschaften x
Props Props x
FAQ FAQ -
lifecycle methods Lifecycle-Methoden -
pure functions pure functions -
impure functions impure functions -
View-Hierarchie - -
Guide Leitfaden x
Try it on CodePen Probier es auf CodePen aus
Frontend Build Pipeline
out of the box
Package Manager
third-party packages Pakete von Drittanbietern
toolchain Werkzeugkette or Werkzeuge x
keys Keys or Schlüssel x
Shallow Renderer Shallow Renderer or flaches rendern
root Root
root element Root-Element
@miku86
Copy link
Member

miku86 commented Feb 11, 2019

Personally, I don't use templates in the React context, more in the Vue context, so I would go with Vorlagen.

I think polyfill is a neologism, that can't get translated.

I always use state, because it's deeply coupled with React, like in setState().
I translated state with Zustand, but now I think that staying with the original state perhaps would be better.

In general, I'm a big fan of using the originals.

@ChrisB9
Copy link
Collaborator

ChrisB9 commented Feb 11, 2019

i completely agree with you for the polyfill and state part but the template is a difficult one. Vorlage reminds me a lot of a letter or an e-mail, something where you just fill in the blanks.. it doesn't seem right in context of react

@ChrisB9
Copy link
Collaborator

ChrisB9 commented Feb 11, 2019

@ph1p Setup should stay "Setup"

  • I think Properties goes along with State - they just belong to react
  • immutability

@ph1p
Copy link
Member Author

ph1p commented Feb 25, 2019

Should we add Guide instead of Leitfaden or Handbuch?

@miku86
Copy link
Member

miku86 commented Feb 25, 2019

Should we add Guide instead of Leitfaden or Handbuch?

Handbuch klingt im alltäglichen Sprachgebrauch fremd.
Ich finde Leitfaden oder auch einfach Anleitung gut.

@JohannesKlauss
Copy link
Contributor

@ph1p I'd say for Guide or Leitfaden. Handbuch would imply to much I think.

How should we translate single-page apps? As SPA and imply that the reader knows what that means? I can't really think of a german translation that would sound smooth and make sense.

@ph1p
Copy link
Member Author

ph1p commented Feb 25, 2019

First paragraph on this site https://reactjs.org/docs/glossary.html. I think we should use Single-Page Applications and SPA as it is. Sometimes there are words we also do not translate into german like State-Management, Deployment, Server-Side Rendering (SSA), Hot Module Reloading (HMR), High Ordered Components (HOC) or something else.

Perhaps we will translate some of them, based on their context, and mention the english wording.

@ChrisB9
Copy link
Collaborator

ChrisB9 commented Feb 26, 2019

i saw it on the russian translation page (translation.md): a file dedicated for this sole purpose so it doesnt get lost in issues
What do you think?

@ph1p
Copy link
Member Author

ph1p commented Feb 26, 2019

Spanish and Brazilian also. We should add that too. At the beginning I wasn't sure what we can add, change or delete in this repository.

@do-wa
Copy link

do-wa commented Mar 13, 2019

I think this is the right ticket for this kind of questions, because I'm facing some difficulties in terms of translating some react specific words:
root ReactComponent
Ursprungs ReactComponent ?
oberste ReactComponent ?
I think the literal translation "Wurzel" isn't helpful.

hydrate
I saw that the verb render is translated by others in "denglish" with "gerendet" , "rendert" etc.
Is there any alternative to "hydraten" or a completely different word?
Also, "hydrieren" does exists as a verb so maybe it's a good idea to stick with the translation

@JohannesKlauss
Copy link
Contributor

JohannesKlauss commented Mar 14, 2019

I'd say Root ReactComponent: React Wurzelkomponente
The image of an tree as in component tree is also present in german and a lot of IT stuff in german uses words like Wurzel, Blatt, Ast, Abzweigung to describe trees.

@ph1p ph1p closed this as completed Mar 14, 2019
@ph1p ph1p reopened this Mar 14, 2019
@JohannesKlauss
Copy link
Contributor

I don't think Ursprungs-Komponente is correct, since it implies it's the component all other components are derived from, which is not the case.

@iamstiil
Copy link

iamstiil commented Apr 1, 2019

What could be the correct way to translate mount, mounted, unmount and unmounted?

Reference:
https://github.com/reactjs/de.reactjs.org/blame/master/content/docs/reference-react-component.md#L148

@ph1p
Copy link
Member Author

ph1p commented Apr 2, 2019

What could be the correct way to translate mount, mounted, unmount and unmounted?

Reference:
https://github.com/reactjs/de.reactjs.org/blame/master/content/docs/reference-react-component.md#L148

Hi! I think we should use gemounted and geunmounted. A little bit of denglisch. Because it's important to keep the context with all lifecycle methods. I'm assuming no one can do anything with "montieren/befestigen/abmontieren"

@ameetmadan
Copy link
Contributor

ameetmadan commented Apr 25, 2023

How about props and state? I have left them in english until now considering they are not necessarily needed to be translated as the code on the pages is in English as well.

@ChrisB9
Copy link
Collaborator

ChrisB9 commented Apr 25, 2023

Props and State in english - they are already in that list

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