Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update and complete German translation and fix mistakes #1973

Closed
wants to merge 2 commits into from

Conversation

Wuzzy2
Copy link
Contributor

@Wuzzy2 Wuzzy2 commented Dec 14, 2014

This PR updates the German translation, completes it (100% translated) and fixes some grammatical and typographical mistakes.

@@ -2,25 +2,25 @@
# Copyright (C) 2011 celeron
# This file is distributed under the same license as the minetest-c55 package.
# Constantin Wenger <constantin.wenger@googlemail.com>, 2011.
#
# Wuzzy <almikes@aol.com>, 2014.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No other translator is listed here...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automatically generated by Virtaal, sorry.

@BlockMen
Copy link
Contributor

Please update, especially revert the dots "..."
Concerning the hyphenation, either "Mod Informationen" or "Mod-Informationen", but not "Modinformationen".

@Wuzzy2
Copy link
Contributor Author

Wuzzy2 commented Feb 21, 2015

Oh, BlockMen …

  • “Mod Informationen”, “Online Mod Archiv”, “Mod Archiv”: All wrong, this is the Deppenleerzeichen. https://de.wikipedia.org/wiki/Leerzeichen_in_Komposita
  • You might however argue for “Mod-Informationen” over “Modinformationen”. But at the end of the day, this is not much of a difference.
  • Using the “ASCII quote” as quotation marks: Sorry, this is simply wrong in German, and your personal preference is not going to change that. How is clearness even an argument here? Either „…“ or »…«, but not "…". The only valid counter-argument would be valid character encoding or font concerns.
  • What's wrong with the ellipsis character, anyways? Are there real (not just maybe) encoding or font problems?

Anyways, this PR is now really outdated and messy. A couple of new strings have been added lately. So I guess I just throw this PR away and start over, considering the reasonable comments this time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants