Quick question, quick answer.

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.

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? :)

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.

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

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

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

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

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

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)

@ph1p

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

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.

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

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.

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

Yes, I would only translate the texts.

Should we squash PRs?

If it has many commits I think yes..

@miku86

@miku86 @ph1p
<Welcome name="Sara" /> <Welcome name="Cahal" /> <Welcome name="Edite" />

How we name example users:

?
?
?

I changed one example from Taylor to Thomas,
but I think it doesn't matter that much.

I believe it makes sense to only translate code comments and otherwise leave the code as is.

For example instead of:

import React, { useState } from 'react';

function Example() {
  // Declare a new state variable, which we'll call "count"
  const [count, setCount] = useState(0);

  return (
    <div>
      <p>You clicked {count} times</p>
      <button onClick={() => setCount(count + 1)}>
        Click me
      </button>
    </div>
  );
}

I would translate it to:

import React, { useState } from 'react';

function Example() {
  // Deklariere eine neue State Variable, die wir "count" nennen
  const [count, setCount] = useState(0);

  return (
    <div>
      <p>You clicked {count} times</p>
      <button onClick={() => setCount(count + 1)}>
        Click me
      </button>
    </div>
  );
}

It would be too risky to introduce accidental errors as well as diverging from the intended meaning.

Is it really that common to write React in another language than English?

I believe it makes sense to only translate code comments and otherwise leave the code as is.

We took a look at the other repos and they translated the code and sometimes they didn't.
I think we should translate comments and plaintext, but not function names, components or class names.

Examples:
https://pt-br.reactjs.org/
https://pt-br.reactjs.org/docs/handling-events.html
https://fr.reactjs.org/docs/handling-events.html
https://fr.reactjs.org/docs/hello-world.html

Somtimes not:
https://nl.reactjs.org/docs/hello-world.html

@tesseralis

I think we should translate comments and plaintext, but not function names, components or class names.

That appears to be a good compromise. However, what's the official (if any) recommendation, @tesseralis?

That sounds fine. As long as you're consistent. Just keep in mind that sometimes strings refer to data and shouldn't be translated.

Hi! I'm wondering what would be the best way to translate "to mangle". Any ideas?
These are the two sentences:

Finally, the resulting bundle is piped to uglify-js for mangling (read why):
Schließlich wird das so entstandene Bundle an uglify-js geleitet, um xxxxx zu werden.

The uglify plugin compresses and mangles the final bundle:
Das uglify-Plugin komprimiert und xxxxx das finale Bundle.

By the way, should we remove the "in progress" and "needs review" labels from merged pull requests? Looks a bit confusing :-)

Hi! I'm wondering what would be the best way to translate "to mangle". Any ideas?
These are the two sentences:

Finally, the resulting bundle is piped to uglify-js for mangling (read why):
Schließlich wird das so entstandene Bundle an uglify-js geleitet, um xxxxx zu werden.

The uglify plugin compresses and mangles the final bundle:
Das uglify-Plugin komprimiert und xxxxx das finale Bundle.

Since mangling is the process of shortening variable names I would suggest something like "verkürzt Variablenamen".

a few words / phrases i see while translating which are not clear to me how to translate

original = prefered Translation | alternative

full-stack = Fullstack
app = Anwendung || App
template = Template || Vorlage (saw this above)
react-based = auf React basierend || auf React aufbauend
output = Output || Ausgabe
default = Default || Standardwert
command = Befehl || Kommando

Navigation Menu

Repository navigation

Quick question, quick answer. #4

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Quick question, quick answer. #4

Description

Activity

miku86 commented on Feb 11, 2019

ph1p commented on Feb 11, 2019

miku86 commented on Feb 11, 2019

ph1p commented on Feb 11, 2019

miku86 commented on Feb 11, 2019

ph1p commented on Feb 11, 2019

ph1p commented on Feb 11, 2019

ChrisB9 commented on Feb 11, 2019

ChrisB9 commented on Feb 11, 2019

ph1p commented on Feb 11, 2019

ChrisB9 commented on Feb 11, 2019

ChrisB9 commented on Feb 11, 2019

ph1p commented on Feb 11, 2019

miku86 commented on Feb 11, 2019

ph1p commented on Feb 13, 2019

ChrisB9 commented on Feb 13, 2019

ChrisB9 commented on Feb 18, 2019

miku86 commented on Feb 19, 2019

markus-willems commented on Feb 26, 2019

ph1p commented on Feb 26, 2019

markus-willems commented on Feb 26, 2019

tesseralis commented on Feb 26, 2019

damienxy commented on Mar 7, 2019

damienxy commented on Mar 7, 2019

do-wa commented on Mar 18, 2019

ThomasSpornraft commented on Apr 30, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions