Quick question, quick answer.

[miku86]

Hey folks,

please use this issue to ask all kind of small questions.

Example: "How would you translate 'library' into german?"
Please also provide some context, if necessary.

[miku86]

How would you translate "Learn Once, Write Anywhere" into german?

The context is: "We don’t make assumptions about the rest of your technology stack, so you can develop new features in React without rewriting existing code. React can also render on the server using Node and power mobile apps using React Native."

My current best attempt: "Einmal lernen, für jede Plattform schreiben".
This would align with the second sentence (server & mobile).

What do you think about it? :)

[ph1p]

This thread is definitely useful. I hope it won't get too bloated in the future ^^

Sometimes it's really difficult to find the right words. I think your solution is good (:
But I wrote a few sentences together so you could have a wider range of ideas.

"Einmal lernen, einmal schreiben"
"Einmal lernen, überall benutzen"
"Einmal lernen für alle Systeme"
"Einmal schreiben, überall verwenden"

It is also used in this blog article: content/blog/2015-03-26-introducing-react-native.md. If you haven't already seen it yet.
It's like a catchy slogan.

[miku86]

Thank you. The blog article is really interesting:
"It's worth noting that we're not chasing “write once, run anywhere.” Different platforms have different [...], we should still be developing discrete apps for each platform, but the same set of engineers should be able to build applications for whatever platform they choose, without needing to learn a fundamentally different set of technologies for each. We call this approach “learn once, write anywhere.”

[ph1p]

Should we stay with "Hello, world!" or use "Hallo, Welt!" ?

[miku86]

I changed the code example to "Hallo, Welt" and the user name to "Thomas".

The folks at the french translation also changed their texts to french texts:
https://github.com/reactjs/fr.reactjs.org/blob/master/content/home/examples/a-component-using-external-plugins.js

[ph1p]

Alrighty. I'll update the "Hello world" page.

[ph1p]

Should we translate "Note:" to "Notiz:" or do we prefer an other word like "Merke:" or something else?

[ChrisB9]

But just for texts right? Because i think, renaming function calls and variables felt really awkward...

Should we do a glossary on what Terms we use as default values for let's say Names 'n stuff?
(I think it would be really difficult after some time to find the right words in here)

[ChrisB9]

@ph1p i think a better alternative to "Notiz" is "Hinweis" - what do you think?

[ph1p]

Should we do a glossary on what Terms we use as default values for let's say Names 'n stuff?

This is great idea. I've opened an issue. We can edit it like the first one. #10

i think a better alternative to "Notiz" is "Hinweis" - what do you think?

That's definitely better.

[ChrisB9]

Should we use State as an english term, because it is the common word for it or should we translate it into Zustand?

[ChrisB9]

Same question for Template and Vorlage

[ph1p]

Should we use State as an english term, because it is the common word for it or should we translate it into Zustand?
Same question for Template and Vorlage

I was thinking about the same. I've written "Zustandskomponenten" instead of "state components" and it feels wrong. Maybe this is because we've already worked with react.

Anyway. I think these are context specific words and we should see if it makes sense or not. But maybe with more and more texts we get a feeling for what's right.

[miku86]

But just for texts right? Because i think, renaming function calls and variables felt really awkward...

Yes, I would only translate the texts.