Feature: Implement full Internationalization (i18n) support (en/zh) #440
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.
Description
📝 Description
This PR implements full Internationalization (i18n) support for the opcode application, enabling multi-language interface capabilities. The implementation includes the integration of the
react-i18nextframework, complete translation resources for English and Simplified Chinese, and the migration of core components to use the new translation system.Key Changes:
react-i18nextwithi18nextcore, including language checking and extraction tools (i18next-parser).AgentCard,ProjectCard,SettingsDialog).🔧 Approach
react-i18nextfor React bindings andi18next-browser-languagedetectorfor automatic language detection.common,agents,settings, etc.) matching the feature modules for better maintainability.i18next-parserto automate the extraction of translation keys.🧪 Verification & Testing
All tests passed successfully (See details in
.zcf/test-reports/2026-02-01_i18n-implementation-test.md).i18next,react-i18next,i18next-browser-languagedetector, andi18next-parser(dev).