Repository navigation
feat: Improve the Chinese translation - #855
only4copilot wants to merge 1 commit into
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge OverviewThis PR improves Chinese (zh-CN) translations across the application. The changes include:
Files Reviewed (2 files)
AssessmentThe translation improvements are appropriate and consistent with Chinese localization best practices. The No issues found. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the .gitignore to exclude IDEA configuration files and provides comprehensive Chinese (zh-CN) translation improvements. Key changes include the full localization of the cache management section, standardization of technical terms like "Tokens" and "策略" (Policy), and the addition of new strings for account auto-disabling features. Feedback was provided regarding translation consistency for API key labels, proper capitalization of brand names, and fixing rich text tag syntax in the cache behavior descriptions to prevent rendering issues in the UI.
| "accountId": "账户 ID", | ||
| "alias": "别名", | ||
| "apiKeyId": "API Key ID", | ||
| "apiKeyId": "API 密钥 ID", |
There was a problem hiding this comment.
The translation of "API Key" has been updated to "API 密钥" in this line, but the adjacent keys apiKeyName (line 66) and apiKeySecret (line 67) still use the English term "API Key". It is recommended to update them as well to maintain consistency across the UI.
| "providerTimeoutAria": "{provider} 超时毫秒", | ||
| "removeProviderOverrideAria": "删除 {provider} 覆盖", | ||
| "newProviderNamePlaceholder": "例如谷歌、开放式...", | ||
| "newProviderNamePlaceholder": "例如 google、openai...", |
There was a problem hiding this comment.
Brand names like "Google" and "OpenAI" should follow proper capitalization to be consistent with other parts of the translation (e.g., lines 2423 and 2784).
| "newProviderNamePlaceholder": "例如 google、openai...", | |
| "newProviderNamePlaceholder": "例如 Google、OpenAI...", |
| "misses": "未命中次数", | ||
| "total": "总计", | ||
| "behaviorDeterministic": "仅缓存 temperature=0 的非流式请求。", | ||
| "behaviorBypass": "通过请求头 {header} 绕过缓存。", |
There was a problem hiding this comment.
This key is used with t.rich in src/app/(dashboard)/dashboard/cache/page.tsx (line 514), which expects a rich text tag (e.g., <header />) instead of a variable placeholder ({header}). The current syntax will cause the literal string {header} to be displayed in the UI instead of the intended code block.
| "behaviorBypass": "通过请求头 {header} 绕过缓存。", | |
| "behaviorBypass": "通过请求头 <header /> 绕过缓存。", |
| "behaviorDeterministic": "仅缓存 temperature=0 的非流式请求。", | ||
| "behaviorBypass": "通过请求头 {header} 绕过缓存。", | ||
| "behaviorTwoTier": "双层存储：内存 LRU（快速）+ SQLite（重启后持久化）。", | ||
| "behaviorTtl": "默认 TTL：30 分钟。可通过 {envVar} 配置。", |
There was a problem hiding this comment.
This key is used with t.rich in src/app/(dashboard)/dashboard/cache/page.tsx (line 524), which expects a rich text tag (e.g., <envVar />) instead of a variable placeholder ({envVar}). The current syntax will cause the literal string {envVar} to be displayed in the UI instead of the intended code block.
| "behaviorTtl": "默认 TTL：30 分钟。可通过 {envVar} 配置。", | |
| "behaviorTtl": "默认 TTL：30 分钟。可通过 <envVar /> 配置。", |
|
Thanks @only4copilot for this great contribution! 🎉 The improvements have been integrated into the |
3 participants
No description provided.