docs: update zh-TW translation instructions based on PR #6946 learnings #7001
Conversation
![roomote[bot]](https://avatars.githubusercontent.com/in/1546624?s=60&v=4){kind=small}
- Added comprehensive terminology mapping with notes - Included new terms learned from native speaker improvements - Added consistency guidelines for formality and punctuation - Provided examples of good vs bad translations - Added review checklist for quality assurance Based on improvements by @PeterDaveHello in PR #6946
dosubot
bot
added
the
size:M
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
| | prompt | 提示詞 | 提示 | Add 詞 for AI prompts | | ||
| | documentation | 說明文件 | 文件 | Use 說明文件 for docs | | ||
| | endpoint | 端點 | 站點 | Use 端點 for API endpoints | | ||
| | learn more | 了解更多 | 瞭解更多 | Use simplified 了 | |
There was a problem hiding this comment.
The note for the 'learn more' row says 'Use simplified 了'. This wording is ambiguous—please clarify what is meant by 'simplified 了' so translators understand the intended usage.
| | learn more | 了解更多 | 瞭解更多 | Use simplified 了 | | |
| | learn more | 了解更多 | 瞭解更多 | Use 了 instead of 瞭 for 了解更多 | |
There was a problem hiding this comment.
We can ignore this one for this scope this time.
| | learn more | 了解更多 | 瞭解更多 | Use simplified 了 | | ||
| | approve | 核准 | 批准 | Use 核准 for approvals | | ||
| | global | 全域 | 全局 | Use 全域 for scope | | ||
| | level | 層級 | 級 | Use 層級 for hierarchy | | ||
|
|
||
| ## Formatting Rules | ||
|
|
||
| - Add spaces between Chinese and English/numbers: "AI 驅動" (not "AI驅動") | ||
| - Use Traditional Chinese quotation marks: 「範例文字」(not "範例文字") |
There was a problem hiding this comment.
Consider using full-width parentheses for consistency with Chinese typography: instead of mixing full-width and half-width punctuation.
| - ✅ "登入 Roo Code Cloud" (clearer intent) | ||
|
|
||
| - ❌ "基於工作、Token 和成本的使用指標" | ||
| - ✅ "基於工作任務、Token 和成本的用量指標" (more precise) |
There was a problem hiding this comment.
Is "工作任務" redundant here? Since "任務" already means task/work, could we simplify to just "基於任務、Token 和成本的用量指標"?
There was a problem hiding this comment.
That’s true to some extent, but sometimes it’s to avoid being too literal and to ensure smooth reading.
| - [ ] Ensure proper spacing between Chinese and English text | ||
| - [ ] Confirm appropriate formality level (您 vs 你) | ||
| - [ ] Validate that technical terms are handled consistently | ||
| - [ ] Review context to ensure translations make sense in the UI |
There was a problem hiding this comment.
The zh-CN instructions file includes additional sections like Technical Documentation Guidelines and Best Practices (278 lines vs 95 here). Would it be valuable to adapt some of those comprehensive sections for zh-TW in a future update?
There was a problem hiding this comment.
Maybe, but it will also take more time and effort to review. Additionally, LLM translations still have their limitations, especially for languages with a lower proportion of users, such as Traditional Chinese.
| | learn more | 了解更多 | 瞭解更多 | Use simplified 了 | | ||
| | approve | 核准 | 批准 | Use 核准 for approvals | | ||
| | global | 全域 | 全局 | Use 全域 for scope | | ||
| | level | 層級 | 級 | Use 層級 for hierarchy | |
There was a problem hiding this comment.
Based on the zh-CN file, consider adding translations for commonly used terms like:
- checkpoint (存檔點 vs 檢查點)
- diff (差異更新 vs 差分)
- cache (快取 vs 緩存)
- rate limit (請求頻率限制 vs 速率限制)
These appear frequently in the codebase and would benefit from standardized translations.
There was a problem hiding this comment.
The examples here seem to mix (without clearly distinguishing) the usage of Traditional and Simplified Chinese, so let’s just skip it for now. This isn’t really something that an LLM is particularly good at.
|
@PeterDaveHello does this look good in general? Should we merge? Thank you for your help! |
| ### Action Verbs | ||
|
|
||
| - Create/Build: 建立 | ||
| - Delete/Remove: 刪除 |
|
|
||
| ### Action Verbs | ||
|
|
||
| - Create/Build: 建立 |
There was a problem hiding this comment.
Build ... depends on the context.
|
|
||
| - Create/Build: 建立 | ||
| - Delete/Remove: 刪除 | ||
| - Update/Modify: 更新 |
| - ✅ "使用額外內容強化提示詞" | ||
|
|
||
| - ❌ "線上工作歷歷史記錄" (typo) | ||
| - ✅ "線上工作歷史紀錄" |
|
|
||
| Before submitting translations: | ||
|
|
||
| - [ ] Check for typos and repeated characters |
|
@mrubens I left my comments ;) |
daniel-lxs
moved this from PR [Needs Review]
to PR [Changes Requested]
in Roo Code Roadmap
|
@roomote-agent Use switch_mode to switch to pr-fixer mode and solve the issues on this PR. Do not create a new one. Keep @PeterDaveHello's advice into consideration. |
|
Hi @daniel-lxs! I've received your request and I'm now working on fixing the issues identified by @PeterDaveHello. I'll apply the suggested changes to the zh-TW translation instructions and push the updates to this PR branch. Will keep you posted on the progress! |
…ructions - Removed duplicate level entry from terminology table - Added note that Build translation depends on context - Added separate entries for Remove (移除) and Modify (修改) - Fixed typo in example (removed extra 歷 character) - Simplified checklist item about checking for typos Co-authored-by: PeterDaveHello <[email protected]>
|
Hi @daniel-lxs and @PeterDaveHello! I've successfully applied all the feedback from @PeterDaveHello's review to the zh-TW translation instructions. Here's what was changed in commit f7bad5c: Changes Applied:✅ Line 26: Removed the duplicate "level" entry from the terminology table All CI checks have passed successfully! The PR is ready for final review. Thank you @PeterDaveHello for your valuable feedback on improving the Traditional Chinese translation guidelines! 🙏 |
| | pin/unpin | 釘選/取消釘選 | 置頂/取消置頂 | Use 釘選 for UI pinning | | ||
| | enhance | 強化 | 增強 | Use 強化 for improvements | | ||
| | prompt | 提示詞 | 提示 | Add 詞 for AI prompts | | ||
| | documentation | 說明文件 | 文件 | Use 說明文件 for docs | |
There was a problem hiding this comment.
This might depend on the context to determine what sounds smoother, so it’s better not to hardcode it in advance.
| ### Action Verbs | ||
|
|
||
| - Create: 建立 | ||
| - Build: 建立 (depends on context) |
There was a problem hiding this comment.
“建置” maybe… at least it can be distinguished from "Create".
…iguous 'learn more' note
|
Hey @PeterDaveHello Should we merge this or do you think we should make more adjustments? |
This PR updates the Traditional Chinese (zh-TW) translation instructions based on the excellent improvements made by @PeterDaveHello in PR #6946.
Changes Made
📚 Enhanced Terminology Mapping
✨ Added Consistency Guidelines
📝 Included Common Patterns
✅ Added Examples and Review Checklist
Context
As requested by @mrubens in this comment, this PR captures the learnings from the native speaker improvements to help future translators maintain consistency and quality.
Related Issues
cc @mrubens @PeterDaveHello
Important
Updates zh-TW translation guidelines with new terminology, consistency rules, common patterns, examples, and a review checklist.
This description was created by
for 3ed0a56. You can customize this summary. It will automatically update as commits are pushed.