Major German translation rework (01/12/2024) #7612
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a major translation work of the German translation. I felt this was neccessary because of many mistakes and just missing translations.
Mistakes in current German translation (that this PR fixes, hopefully) include:
After my first failed attempt to update the German translation (#7602), I’ve had another go under
master
.I used
lupdate
and some manual merging of my previous work to get this done.This was my
lupdate
line:lupdate -locations none -I include plugins plugins/* plugins/*/* src/* src/*/* -ts data/locale/de.ts
This is loosely based on what I found in CMake files and I'm not sure if this line captures every string in LMMS, but it seems close. If I missed an important directory, please let me know. The line looks a bit flawed IMO. I would love to know the correct lupdate line. Unfortunately, I'm not very good in reading CMake yet.
(I intentionally removed the
-no-obsolete
argument because it deletes old translations. It is generally a bad idea to delete obsolete translations by default because obsolete translations can still be useful for translators to pick up similar translators. Especially if modules get moved and renamed around all the time. Qt Linguist is quite powerful in that regard. The only case where I recommend this argument is when a translation is complete or near-complete. It's only text, the few bytes you save aren't worth it IMO.)Features:
The translation is not complete, but it's about 3000/3200. There are many very difficult strings which seem to require expert knowledge. It would be nice if strings had context and/or translator comments (a core feature of the Qt translation system).
This translation was extensively tested at commit 3562bbe. Feel free to do the same.