feat(i18n): localize zh-CN UI and migrate hardcoded strings - #153
Merged
Conversation
Feat/i18n support
Feat/i18n support
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
2 participants
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 migrates hardcoded user-facing strings into the project’s i18n resource system and completes the Chinese (zh-CN) translation pass for the affected UI.
Changes
replace hardcoded text with translation keys
add missing Chinese translations for the current UI
improve consistency and maintainability of localized strings
Scope
This change is focused on zh-CN localization and the impacted interface surfaces. It does not attempt to fully complete every other locale in the project.
Validation note
The repository’s i18n validation checks all locales for missing keys, extra keys, and untranslated values that still match the English source. While the zh-CN locale is substantially complete, other locale files and remaining untranslated entries still prevent the full project-wide validation from passing. This is a repository-wide locale completeness issue rather than a functional defect in the current change.