Add Full i18n Coverage: 18 Languages, 1914 Common Keys, 1243 Settings Keys #3240
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
This PR significantly expands Dokploy’s internationalization (i18n) support. It adds complete translations for 18 languages, covering both the common strings and the settings module, with special focus on high‑quality Chinese translations (reviewed and proofread).
What’s Included
New language coverage
Added full translations for 18 languages across the app.
Ensured consistent terminology and tone across all locales.
Common i18n keys
Added/updated 1,914 common i18n key‑value pairs.
Covered general UI labels, navigation, actions, error messages, and helper texts.
Settings module i18n
Added/updated 1,243 i18n key‑value pairs specifically for the settings section.
Includes monitoring, git providers, authentication, and other settings‑related screens.
Chinese translations
Chinese (Simplified) is thoroughly completed and polished.
All Chinese strings have been proofread for accuracy, consistency, and clarity.
Focus on keeping technical terms clear while using natural, user‑friendly language.
Notes
No breaking changes to the i18n key structure are intended; existing keys are preserved where possible.
If any upstream keys were missing or ambiguous, they have been normalized to improve consistency across locales.
Please pay particular attention during review to:
Naming of any newly introduced keys.
Potential overlaps or duplicates with existing i18n entries.