fix(i18n): zh-TW - #4309
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughThis PR standardizes Traditional Chinese wording across documentation and localization: it updates terminology and phrasing in Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
i18n/locales/zh-TW.yaml (2)
34-34:⚠️ Potential issue | 🟡 MinorTerminology inconsistency:
封禁vs封鎖.
oauth.user_banned(Line 243) anduser.username_or_password_error(Line 69) were normalized to封鎖, butauth.user_bannedhere still uses封禁. For consistency across the locale, consider updating this line as well.Proposed change
-auth.user_banned: "使用者已被封禁" +auth.user_banned: "使用者已被封鎖"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/locales/zh-TW.yaml` at line 34, The key auth.user_banned uses the term "封禁" which is inconsistent with other keys (oauth.user_banned and user.username_or_password_error) that use "封鎖"; update the auth.user_banned value to use "封鎖" so terminology is consistent across the zh-TW locale, ensuring you edit the auth.user_banned entry in i18n/locales/zh-TW.yaml to match the normalized wording.
156-156:⚠️ Potential issue | 🟡 Minor
當前→目前missed here.
redemption.expire_time_invalid(Line 62) andpayment.not_configured(Line 128) were updated to目前, butchannel.upstream_saturatedstill uses當前分組. Consider aligning.Proposed change
-channel.upstream_saturated: "當前分組上游負載已飽和，請稍後再試" +channel.upstream_saturated: "目前分組上游負載已飽和，請稍後再試"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/locales/zh-TW.yaml` at line 156, The string for key channel.upstream_saturated uses "當前分組上游負載已飽和，請稍後再試" but should use the consistent term "目前" like other entries; update the value in channel.upstream_saturated to "目前分組上游負載已飽和，請稍後再試" so it matches the wording used in redemption.expire_time_invalid and payment.not_configured.README.zh_TW.md (1)
47-47:⚠️ Potential issue | 🟡 MinorBroken in-page anchor:
#-主要特性.The heading was renamed from
主要特性to主要功能at Line 178, but the top-of-README quick-nav still links to#-主要特性. GitHub's auto-generated anchor will no longer match, so this link is dead.Proposed fix
- <a href="#-主要特性">主要特性</a> • + <a href="#-主要功能">主要功能</a> •🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.zh_TW.md` at line 47, Update the broken in-page anchor link by replacing the href value "#-主要特性" in the top navigation link element (<a href="#-主要特性">主要特性</a>) with the new auto-generated anchor for the renamed heading ("主要功能"), i.e. change the href to "#-主要功能" so the quick-nav link matches the actual heading text "主要功能".
🧹 Nitpick comments (1)
README.zh_TW.md (1)
186-186: Minor:使用者界面vs介面.The PR normalizes
接口→介面across the document. On this line the text still reads使用者界面設計. In zh-TW both界面and介面are acceptable, but for consistency with the rest of the file consider使用者介面設計. Non-blocking.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.zh_TW.md` at line 186, The line containing "🎨 全新 UI | 現代化的使用者界面設計" uses 界面 while the PR standardized on 介面; update that string to "🎨 全新 UI | 現代化的使用者介面設計" so it matches the rest of the document's use of 介面.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@i18n/locales/zh-TW.yaml`:
- Line 42: Normalize inconsistent verb usage by replacing 獲取 with 取得 in the
zh-TW locale entries; update the keys/values such as token.get_info_failed,
channel.get_list_failed, channel.get_tags_failed, channel.get_key_failed,
channel.get_ollama_failed, channel.get_available_failed, model.get_list_failed,
model.get_failed, and distributor.get_channel_failed so their messages use 取得
instead of 獲取, ensuring the rest of each string remains unchanged and preserving
YAML quoting/formatting.
- Line 93: The key user.topup_processing still uses the term "充值" instead of the
normalized "儲值"; update the value for user.topup_processing to use "儲值" so it
matches the other topup.* messages and payment.not_configured entries (i.e.,
replace "充值處理中，請稍後重試" with the normalized "儲值處理中，請稍後重試" under the
user.topup_processing key).
In `@README.zh_TW.md`:
- Line 448: Replace the string "本項目採用" with "本專案採用" in the README line that
currently reads "本項目採用 [GNU Affero 通用公共許可證 v3.0 (AGPLv3)](./LICENSE) 授權。";
update the text so it reads "本專案採用 [GNU Affero 通用公共許可證 v3.0 (AGPLv3)](./LICENSE)
授權。", preserving the existing license link and punctuation.
---
Outside diff comments:
In `@i18n/locales/zh-TW.yaml`:
- Line 34: The key auth.user_banned uses the term "封禁" which is inconsistent
with other keys (oauth.user_banned and user.username_or_password_error) that use
"封鎖"; update the auth.user_banned value to use "封鎖" so terminology is consistent
across the zh-TW locale, ensuring you edit the auth.user_banned entry in
i18n/locales/zh-TW.yaml to match the normalized wording.
- Line 156: The string for key channel.upstream_saturated uses
"當前分組上游負載已飽和，請稍後再試" but should use the consistent term "目前" like other entries;
update the value in channel.upstream_saturated to "目前分組上游負載已飽和，請稍後再試" so it
matches the wording used in redemption.expire_time_invalid and
payment.not_configured.
In `@README.zh_TW.md`:
- Line 47: Update the broken in-page anchor link by replacing the href value
"#-主要特性" in the top navigation link element (<a href="#-主要特性">主要特性</a>) with the
new auto-generated anchor for the renamed heading ("主要功能"), i.e. change the href
to "#-主要功能" so the quick-nav link matches the actual heading text "主要功能".
---
Nitpick comments:
In `@README.zh_TW.md`:
- Line 186: The line containing "🎨 全新 UI | 現代化的使用者界面設計" uses 界面 while the PR
standardized on 介面; update that string to "🎨 全新 UI | 現代化的使用者介面設計" so it matches
the rest of the document's use of 介面.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 32f07260-3840-46d8-ae14-366fec4f8cb4
📒 Files selected for processing (3)
README.zh_TW.mdi18n/locales/zh-TW.yamlweb/src/i18n/locales/zh-TW.json
1 participant
Important
📝 变更描述 / Description
修正及潤飾 zh-TW 的錯誤或不通順的翻譯。
🚀 变更类型 / Type of change
🔗 关联任务 / Related Issue
✅ 提交前检查项 / Checklist
Bug fix，我已提交或关联对应 Issue，且不会将设计取舍、预期不一致或理解偏差直接归类为 bug。📸 运行证明 / Proof of Work
(请在此粘贴截图、关键日志或测试报告，以证明变更生效)
Summary by CodeRabbit
Documentation
Chores