[Review only] Changing german translation

[marcelgerber]

These are some changes to use a better style of language in the german samples. Based on the idea in #5583.

For review: @WebsiteDeveloper @pthiess @couzteau @ingorichter
Thanks to @WebsiteDeveloper for first hints.

[marcelgerber]

@ingorichter @couzteau What do you guys think? (as you had the idea to clean up german samples)

[marcelgerber]

Pinging @couzteau and @ingorichter again...

[couzteau]

I don't think we should translate Quick Edit at all. That said if we do, I think "schnelles" should be capitalized, as it is referring to a feature name, thus not used as an adjective.

[couzteau]

Sorry for the belated reply and thanks for tackling the overhaul of the German Getting Started.

[marcelgerber]

Quick View and Quick Edit aren't saying much more than Schnelle Farbansicht and Schnelles Bearbeiten. And letting them sound good in german sentences isn't easy.

[peterflynn]

@SAplayer @couzteau It seems more consistent with our other locales to translate those names -- unless German has some characteristic that makes it less appropriate than in other languages? I usually think of French as our "canonical" translation, because it's the only one written by localization professionals... and they do translate "Quick Open," "Quick View," etc. into French. Fwiw.

[couzteau]

I do preceive the term "Schnelles Berabeiten" as awkward because it sounds like machine translation. It doesn't seem sensitive to the context of working as a web developer in the web stack. There are 100s of terms in your day-to-day work that are english. If I'm the only one that feels this awkwardnes, fine, but it certainly sounds awkward to me.

[marcelgerber]

I believe other translations sound even worse ;)

[couzteau]

That's true, it's a very common problem with localization and it's often a fine line. Cultures are different I don't think there needs to be consistency in how deep the localization goes between i.e. German and French ( @peterflynn 's remark ). I.e. french has a much stronger tradition in going very deep in translation. France used to (may be still has) laws that would require every software vendor to translate everything. Germany never did that.

I'd like to have brackets users a natural experience when using German, that is not so awkward that they'll switch to English because they can.

[marcelgerber]

@couzteau Bur even if we would use Quick Edit, it wouldn't be easy to put them into normal sounding german sentences.
For example, try to form a sentence out of um einen Editor zum Schnellen Bearbeiten anzuzeigen, der Ihnen alle relevanten CSS-Regeln anzeigt..

[couzteau]

In this case I think the following translation would be my preferred translation:
Wenn Sie HTML editieren, können Sie die Tastenkombination Cmd/Strg + E verwenden, um einen Inline-Editor anzuzeigen, der Ihnen alle relevanten CSS-Regeln zum schnellen Berabeiten anzeigt.

[couzteau]

That is, for QuickEdit - I'm sticking with Inline-Editor zum schnellen Bearbeiten - this may work well in other contexts too.

[marcelgerber]

Yes, this is a good translation. But we should stay consistent with our translation names, so we should use the translated one everywhere.

[couzteau]

I agree, there needs to be consistency.

[marcelgerber]

@couzteau Changed some things, please take a look again.

[couzteau]

This is most definitely a big improvement. I'd merge it, but @ingorichter signed up for this review. @ingorichter please go ahead and merge if you have no objections. Thanks @SAplayer

[couzteau]

@ingorichter blessed the change. Merging.