fix(i18n): improve german translation

[essenmitsosse]

• Removes a few anglicisms
• Fixes wrong casing for german footer

Before ("datenschutzerklärung" needs to be capitalized):

@userquin: could you check if there was a specific reason for lower casing this word via CSS? Don't want to break any other language

edit: Also updated the tagline to the new version and made sure we don't get unnecessary line wrapping.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 6, 2026 1:12pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 6, 2026 1:12pm
npmx-lunaria	Ignored		Feb 6, 2026 1:12pm

[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
lunaria/files/de-DE.json	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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request removes the lowercase CSS class from the privacy NuxtLink in AppFooter.vue, increases the home page paragraph max width from max-w-md to max-w-xl, and updates German translations in two locale files to prefer terms like “Aktion/ Aktionen” over “Operation/ Operationen”, replace “Log” with “Protokoll”, and adjust phrasing (e.g., “Features” → “Funktionen”, and “besserer Browser” → “schnellerer, modernerer Browser”). No control-flow, data-handling, or public/exported declarations were changed.

Possibly related PRs

• feat(i18n,ui): add privacy policy page #900: Modifies the same privacy NuxtLink in AppFooter.vue that this PR edits.
• feat(i18n): update German translations #880: Updates the same German locale files (i18n/locales/de-DE.json and lunaria/files/de-DE.json) with overlapping translation keys.
• fix: use latest tag line "better" -> "fast, modern" #1029: Changes homepage tagline and related copy, aligning with the tagline wording updates in this PR.

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description accurately describes the changeset, addressing German translation improvements including anglicism removal, CSS casing fix for 'datenschutzerklärung', tagline updates, and line wrapping prevention.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

lunaria/files/de-DE.json (1)

822-822: ⚠️ Potential issue | 🟡 Minor

Potential inconsistency: account_menu.ops still uses "Operation(en)".

Line 822 reads "{count} Operation | {count} Operationen" while all other occurrences of "Operation" within operations.queue.* have been migrated to "Aktion(en)". If the intent is to replace the anglicism consistently, this key should be updated as well.

If there's a deliberate reason to keep "Operation" here (e.g. it refers to npm CLI operations specifically), it might be worth adding a comment in the PR noting that distinction.

Suggested fix

-    "ops": "{count} Operation | {count} Operationen",
+    "ops": "{count} Aktion | {count} Aktionen",

[userquin]

revert this change, we need to disccuss this, we also have some uppercase usages in headings, or just await core team response

[essenmitsosse]

Thanks for chiming in. I would be fine with uppercase in headings for now, at least regarding German. Lowercase would also be fine if we reeeeally want it, but then the whole footer should be lowercased.

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

i18n/locales/de-DE.json (1)

822-822: ⚠️ Potential issue | 🟡 Minor

Inconsistent terminology: account_menu.ops still uses "Operation/Operationen".

Line 822 still reads "{count} Operation | {count} Operationen", but every other occurrence of this term (lines 453–472) has been updated to "Aktion/Aktionen". This should be aligned for consistency.

Proposed fix

-    "ops": "{count} Operation | {count} Operationen",
+    "ops": "{count} Aktion | {count} Aktionen",

lunaria/files/de-DE.json (1)

822-822: ⚠️ Potential issue | 🟡 Minor

Same inconsistency as in i18n/locales/de-DE.json: account_menu.ops still uses "Operation/Operationen".

Should be updated to match the rest of the "Aktion/Aktionen" terminology.

Proposed fix

-    "ops": "{count} Operation | {count} Operationen",
+    "ops": "{count} Aktion | {count} Aktionen",

[trueberryless]

Awesome enhancements.

I know it's closed already, but why did you replace all "Operationen" with "Aktionen". IMHO "Operationen" fits much better. Idk, for me all the phrases read somehow weird with "Aktionen". Would you (@essenmitsosse ) be so kind and give a little bit more reasoning for your idea regarding this? I'd like to just understand it better 👍

[essenmitsosse]

@trueberryless i didn't even notice this was closed already. Saw it more as a suggestion and wanted to hear some feedback. Honestly we can just roll it back, I'm not really stuck on it.

[trueberryless]

Thanks for the quick reply and feedback. I think I might revert it then - or you, whoever does the next translation ☺️