-
-
Notifications
You must be signed in to change notification settings - Fork 935
feat(i18n): add i18n infrastructure with zh-CN support (v2 — typed keys, locale-aware head, parity test) #729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
xiaoyaner0201
wants to merge
6
commits into
openclaw:main
Choose a base branch
from
xiaoyaner0201:feat/i18n-zh-cn
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
14b7d2d
feat(i18n): add i18n infrastructure with en/zh-CN and translate core …
f39ba23
feat(i18n): extract and translate remaining pages (detail, import, ma…
5a01156
fix(i18n): translate remaining hardcoded strings in skills index, det…
eb07eb4
fix(i18n): guard localStorage/navigator access for SSR compatibility
03058b7
fix(i18n): improve zh-CN translations and address review feedback
cf595f0
fix(i18n): address review feedback — typed keys, locale-aware head, p…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
t()called twice; empty-string contract is implicit and fragilet('footer.an')is evaluated twice in this expression: once to render the word, and again to conditionally add a trailing space. This works becausefooter.anis intentionally set to""(empty string) inzh-CN, but that contract is not enforced anywhere:t()only falls back to English when the resolved value isundefined— an empty string""is returned as-is (seetranslate.ts).zh-CNvalues are non-empty, so an accidental""in a key that should have a translation would silently render nothing.Consider using a single variable or restructuring the key to avoid the double call and make the conditional explicit:
Or better, collapse this into a single key
footer.anSpacewith value"An "(en) /""(zh-CN), removing the two-step pattern entirely.Prompt To Fix With AI