fix(l10n): add German for untranslated strings#105
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Fills the German translation gap for 74 source strings that had no entry in the German l10n files yet (mostly the mobile self-check-in/NFC/QR block in
src/App.vue, subscription/feedback dialogs, and activity strings).l10n/de.json,l10n/de.js,l10n/de_DE.json,l10n/de_DE.js{time},{state},%n, markdown links) and the non-breaking space before…kept byte-for-bytefind_untranslated.pynow reports 0 missing,find_stale.pyreports no orphans,npm run buildpassesNote: this is the intended stopgap from the
l10n-autotranslateskill — entries will be re-matched/overwritten on the next Transifex sync.🤖 Generated with Claude Code