Name Glossary about de.reactjs.org

[ph1p]

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.

[miku86]

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]

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]

Should we add Guide instead of Leitfaden or Handbuch?

[ph1p]

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"

[ChrisB9]

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

[ChrisB9]

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]

@ph1p Setup should stay "Setup"

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

[miku86]

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]

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

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]

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]

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.

[JohannesKlauss]

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]

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

[ameetmadan]

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.