German translation

[katrinleinweber]

• Have you followed the contributing guidelines?
• Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

---

This PR is an on-going effort to provide the German translation. I'm using DeepL.com/translator with some manual smoothing, and shortening of too verbose translations.

Things to discuss (esp. with other German translators)

• Use formal or informal you: Sie or Du?. DeepL defaults to Sie which I'll stick to for now, to speed up the initial translation. Also, that might appeal more to those not already in FLOSS' field of gravity. 💡 other ideas:
  a) Split into a Deutsch (Du) and Deutsch (Sie) or formal/informal translation.
  b) Convert to Du at the end and explain that this more common in the FLOSS community in a note on the first page.
  c) Mix it (randomly).
  d) Shift it from Sie in the first articles to Du in the later ones.
  e) Use some kind of plugin that allows the use to select the variant, factor such phrases out and offer both.
• "Maintainer" or "Betreuer"? DeepL's default is the latter, but I have mingled both expressions a bit.
• "Open-Source-…" & "Pull-Request-…" for compound nouns, but "Open Source" and "Pull Request" when not compounded
• italicize translated quotes (pquote and >) with _ while retaining the original quote below it. That way, German readers can still find the original within the hyperlinked source by copy-pasting a snippet and searching for that.
• Renaming the files (translating the filenames) and adjusting their slugs seems logical, but the other translations retained the English filenames. Presuming that helps the main maintainers, let's mirror the other translators' behavior.
• Prepare file translations on different branches in the fork, and merge them into this de-PR. Then: fix Travis errors here, because PRs in the fork aren't tested. Would that be worth a CI crash course to copy the upstream repo's pipeline?
• change Gemeinde, because that would mean municipality

[katrinleinweber]

PS: If someone turned this bash command into a script that runs slower than the rate limit and replaces one line after the other, we a basic translation could be run over night or a lunch break ;-)

[jens1o]

I think you should not rely on a translation software.

[katrinleinweber]

What do you mean with "rely"?

I argue that utilising it to a) speed up the initial translation and b) experiment with the bash workflow described above is worth the risk and follow-up work of manually "smoothing out" an auto-translation. Which (I think we agree here) is sometimes necessary. However, I experienced DeepL as pretty adept.

Do you maybe feel that the initial "speed up" part is eaten up by not "sometimes" but often more "follow-up work"?

PS: We can of course also switch to German for such discussions among us translators ;-)

[jens1o]

Do you maybe feel that the initial "speed up" part is eaten up by not "sometimes" but often more "follow-up work"?

Yeah, that's the point.

We can of course also switch to German for such discussions among us translators ;-)

I don't care about it, but we can do it if you'd like to.

[katrinleinweber]

Mir ist es auch egal :-D

[MikeMcQuaid]

@katrinleinweber I'm afraid I agree with @jens1o here: I think automatic translation tools are not a good fit for translating this project.

[katrinleinweber]

Are there any mistranslations so far? What I committed so far is slightly proof-read, not the 100% auto-translation. You can compare the latter with the former.

I feel that only a tool and the formal you have been criticized so far, not any specific translation result.

[MikeMcQuaid]

@katrinleinweber I don't speak German so cannot comment on any mistranslations. When this translation is complete I'll have a German friend or coworker review the results and comment.

[kulphol]

Dd

[MikeMcQuaid]

@katrinleinweber Great work, thanks! Could you finish up the remaining test failures and then we should be good to go.

[MikeMcQuaid]

@katrinleinweber Still one more test failure! Note you can run script/test locally to reproduce.

[katrinleinweber]

I did and it yielded only a warning about Node.js'. But that's a common spelling of a possessive form of a word that ends with an s :-/ Worth filing a bug to @retextjs' retext-quotes?

[katrinleinweber]

Ah, there is some green again :-) I'll try to find a better workaround for this s's conundrum, tough.

[MikeMcQuaid]

Worth filing a bug to @retextjs' retext-quotes?

Yeh 👍

[MikeMcQuaid]

Can this be modified like 3dd1596? Thanks!

[MikeMcQuaid]

One more small thing!

[MikeMcQuaid]

Woohoo https://opensource.guide/de/ is live! Incredible work @katrinleinweber 👏!

[katrinleinweber]

You're welcome, and thanks for merging :-) It's also in large parts the work of @jens1o and @Rubinum! 🥇 to them as well, for proof-reading most initial article translations :-)

If any issues or PRs come in regarding the German translation, please feel free to ping me.

Unless people riot about the translation style, I for one will have a look at opensourcefriday.com at some point ;-)

[MikeMcQuaid]

@katrinleinweber That'd be great, please do! It should be much easier/quicker. https://github.com/homebrew/brew.sh could be reviewed too if you're getting bored 😆

[katrinleinweber]

[katrinleinweber]

Follow-ups in #1118

[Burkay5441]

Türk'e