Gitg: Avoid translation of git terminology in German (avoid "Zangendeutsch")
When I first launched Gitg on my (German) system, I had a very awkward experience, as a lot of what the user interface does seemed unclear to me. Turns out that the interface tried come up with own translations for nearly all of Gits terminology, like branches, commits, merges etc. There are no established translations for these things, as git users in Germany use the English terms. The command line tool is translated to German, and it still talks about "Branches", "Commits" etc. in the German translation. When used as an adjective, it conjugates the English terms according to German rules (like "rebasen") – which is pretty much the way most German developers talk about git.
Even if there were official translations for other languages, there are a lot of downsides to translating these things. Searching for these concepts on the Internet for example becomes impossible with translations in any language other than English.
Also, most git users will already have learned the official terminology.
Also, I got amused by some of the translations – "Zweige", "Bereitstellung", "Zusammenführen" almost feels like Zangendeutsch, which is a German Internet meme (popular on Subreddits like ich_iel), which consists of translating everything word by word into German, both as a parody of automatic translation services, and as a parody of some conservatives/"boomers", who see the need for awkward translations of Anglicisms. It might also be a parody of some software vendors like Microsoft, which also inveted some awkward "Zangendeutsch" translations, which never made it into common use (like "Erstellen" (compiling) or "Eingabeaufforderung" (Command line)).
If the translation team agrees with this issue, I'd like to prepare a MR at least for the German translations to use the official git terminology and become more user friendly to German users this way.