i18n(de): add/update German translations

[pitscher]

What does this PR do?

HINT: This is a draft PR. Please do not have a close look yet - I am still working on it.
Reason for it to exist: Avoiding conflicts/doublicate work with other folks attempting to change the German translation.

• This PR adds missing translations for the German language - I am aiming for a 100% coverage.
• Current German coverage (estimate) of this PR: 99% (100% is not yet possible because 2 msgid's are causing issues, see below)
• T.W.I.M.C. I am a native German speaker/writer/citizen :D
• I also updated some already existing (GER) translations because they were either not well phrased or incorrect
• I checked the translations live/using the local demo setup to be aware of the context
• All translations are using the informal "du/dich" wording instead of the very formal "sie/ihr" form. Reason being:
  • "du/dich" establishes are warm/welcoming feel as soon as a user starts using EmDash.
  • I ensured that while using it, the professional tone of EmDash as a software users are supposed to trust is being incorporated. The German language allows this without the need to use the formal "sie/ihr" form.
  • The writing form ("sie" vs. "du") can be adjusted anytime in case the maintainers feel the need to do so (I'm happy to take care of it - although I prefer the informal version for the reason stated above).
• I avoided a mixture of both languages (EN/DE) wherever possible.
  • Example: The translation of "Plugin" for this projects context is "Erweiterung". As someone working in IT, I do not feel happy with this because I am used to English words like "Plugin" - because of my job. However, we should not make the mistake and follow this approach. This would potentially limit the German speaking users of EmDash to folks who do not have issues with a heavy mixture of English and German (=usually IT/Tech folks). Instead, we should aim to provide a native German translation. Result: Folks like me who do prefer the English translation will use it, but folks who do not feel comfortable with English can switch EmDash to German without still being presented with English terms all over the place.

To all bullets above: Feel free to let me know what you think.

My ToDo's prior to requesting a review

• Finalize German translations
• If necessary: Create a new issue for some translation strings (without adjustment a German translation may not always be possible)
• Review all already existing translations again and correct them if necessary (e.g. grammar, wording, ...)
• Perform a final check for consistency to ensure the translations do not differ in the same admin area/context
• Complete the PR checklist below
• If required: rebase my branch to get the latest changes and resolve potential conflicts
• Leave the draft stage of this PR by requesting a review

Issues found

The msgid "Add" & msgid "Edit" can not be translated into German.

See the pictures below to better understand the issue.
TODO - will upload them later.

Closes #

Type of change

• Bug fix
• Feature (requires maintainer-approved Discussion)
• Refactor (no behavior change)
• Translation
• Documentation
• Performance improvement
• Tests
• Chore (dependencies, CI, tooling)

Checklist

• I have read CONTRIBUTING.md
• pnpm typecheck passes
• pnpm lint passes
• pnpm test passes (or targeted tests for my change)
• pnpm format has been run
• I have added/updated tests for my changes (if applicable)
• User-visible strings in the admin UI are wrapped for translation (if applicable). Do not include messages.po changes except in translation PRs — a workflow extracts catalogs on merge to main.
• I have added a changeset (if this PR changes a published package)
• New features link to an approved Discussion: https://github.com/emdash-cms/emdash/discussions/...

AI-generated code disclosure

• This PR includes AI-generated code — model/tool:

Screenshots / test output

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5c57bc0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[github-actions]

Scope check

This PR changes 2,085 lines across 1 files. Large PRs are harder to review and more likely to be closed without review.

If this scope is intentional, no action needed. A maintainer will review it. If not, please consider splitting this into smaller PRs.

See CONTRIBUTING.md for contribution guidelines.

[github-actions]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
packages/admin/src/locales/de/messages.po	Localization changed, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[pitscher]

I have read the CLA Document and I hereby sign the CLA