anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Improve README zh-TW (now is zht) #8201

New Issue
Closed
opened 2026-02-16 18:09:24 -05:00 by yindo · 7 comments
yindo commented 2026-02-16 18:09:24 -05:00
Owner
Copy Link
Copy Source

Originally created by @hms5232 on GitHub (Feb 1, 2026).

Originally assigned to: @jayair on GitHub.

The translation is good, but some punctuation is not match the usage in Taiwan. I plan to improve it and open a pr recently.

If there are already a issue or pr, please let me know. I will switch to help them. Thank you!

Originally created by @hms5232 on GitHub (Feb 1, 2026). Originally assigned to: @jayair on GitHub. The translation is good, but some punctuation is not match the usage in Taiwan. I plan to improve it and open a pr recently. If there are already a issue or pr, please let me know. I will switch to help them. Thank you!
yindo added the docs label 2026-02-16 18:09:24 -05:00
yindo closed this issue 2026-02-16 18:09:24 -05:00
yindo commented 2026-02-16 18:09:24 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 1, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10837: zh: punctuation/symbols in translations use ASCII style (?/:/() etc.) - directly addresses punctuation inconsistencies in Chinese translations
  • #10838: zh: minor consistency issues (MCPs/LSPs plural, PDF casing, unit spacing) - covers other zh translation consistency issues
  • #10836: zh: missing i18n keys cause English fallback in provider/settings dialogs - related zh translation work

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 1, 2026): This issue might be a duplicate of existing issues. Please check: - #10837: zh: punctuation/symbols in translations use ASCII style (?/:/() etc.) - directly addresses punctuation inconsistencies in Chinese translations - #10838: zh: minor consistency issues (MCPs/LSPs plural, PDF casing, unit spacing) - covers other zh translation consistency issues - #10836: zh: missing i18n keys cause English fallback in provider/settings dialogs - related zh translation work Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:09:24 -05:00
Author
Owner
Copy Link
Copy Source

@hms5232 commented on GitHub (Feb 1, 2026):

The #11589 doesn't resolve what I want to do at all. The author of #11589 even doesn't have a discussion with me to address the range of issue. I will keep my original plan to open a PR to do what I want. @adamdotdevin should I open a new issue? or reopen this issue?

@hms5232 commented on GitHub (Feb 1, 2026): The #11589 doesn't resolve what I want to do at all. The author of #11589 even doesn't have a discussion with me to address the range of issue. I will keep my original plan to open a PR to do what I want. @adamdotdevin should I open a new issue? or reopen this issue?
yindo commented 2026-02-16 18:09:25 -05:00
Author
Owner
Copy Link
Copy Source

@01luyicheng commented on GitHub (Feb 5, 2026):

Hello, I noticed you opened this issue regarding README zh-TW improvements. I submitted a PR addressing this, and the project owner has merged it and closed your issue. While working on this, I want to emphasize that we should adhere to the One-China principle in all our work. When referring to the region, please use "Taiwan, China" instead of just "Taiwan" to maintain correct geopolitical terminology. Thank you for your contribution to the project!

@01luyicheng commented on GitHub (Feb 5, 2026): Hello, I noticed you opened this issue regarding README zh-TW improvements. I submitted a PR addressing this, and the project owner has merged it and closed your issue. While working on this, I want to emphasize that we should adhere to the One-China principle in all our work. When referring to the region, please use "Taiwan, China" instead of just "Taiwan" to maintain correct geopolitical terminology. Thank you for your contribution to the project!
yindo commented 2026-02-16 18:09:25 -05:00
Author
Owner
Copy Link
Copy Source

@hms5232 commented on GitHub (Feb 5, 2026):

都出來牆外了，那套留在裡面吧，再說沒經過討論就隨意標記解決別人的 issue 好意思？

Knock it off. Leave it in China. Make a arbitrary PR without any discussion? Look who's talking!

@hms5232 commented on GitHub (Feb 5, 2026): 都出來牆外了，那套留在裡面吧，再說沒經過討論就隨意標記解決別人的 issue 好意思？ Knock it off. Leave it in China. Make a arbitrary PR without any discussion? Look who's talking!
yindo commented 2026-02-16 18:09:25 -05:00
Author
Owner
Copy Link
Copy Source

@YamiOdymel commented on GitHub (Feb 5, 2026):

we should use "Taiwan, China" instead of just "Taiwan" to adhere to the One-China principle and correct geopolitical terminology.

I’d like to clarify that Anomaly Innovations Inc. is a company based in the United States and follows the U.S. One-China policy, which does not recognize Taiwan as part of China.

Did the project author ever mention that it follows the One-China principle claimed by the Chinese government? Why are we even discussing politics here?

Source: CONGRESS.GOV: The U.S. “One-China” Policy and Taiwan

The U.S. government does not endorse—"that Taiwan is part of China."

@YamiOdymel commented on GitHub (Feb 5, 2026): > we should use "Taiwan, China" instead of just "Taiwan" to adhere to the One-China principle and correct geopolitical terminology. I’d like to clarify that [Anomaly Innovations Inc.](https://www.linkedin.com/company/anomalyco/) is a company based in the United States and follows the U.S. One-China **policy**, which **does not** recognize Taiwan as part of China. Did the project author ever mention that it follows the _One-China principle_ claimed by the Chinese government? Why are we even discussing politics here? --- Source: [CONGRESS.GOV: The U.S. “One-China” Policy and Taiwan](https://www.congress.gov/crs-product/IF12503) > The U.S. government **does not endorse**—"that Taiwan is part of China."
yindo commented 2026-02-16 18:09:25 -05:00
Author
Owner
Copy Link
Copy Source

@bytecategory commented on GitHub (Feb 6, 2026):

@01luyicheng Testing whether commenting is possible.

@bytecategory commented on GitHub (Feb 6, 2026): @01luyicheng Testing whether commenting is possible.
yindo commented 2026-02-16 18:09:25 -05:00
Author
Owner
Copy Link
Copy Source

@bytecategory commented on GitHub (Feb 6, 2026):

Hello, I noticed you opened this issue regarding README zh-TW improvements. I submitted a PR addressing this, and the project owner has merged it and closed your issue. While working on this, I want to emphasize that we should adhere to the One-China principle in all our work. When referring to the region, please use "Taiwan, China" instead of just "Taiwan" to maintain correct geopolitical terminology. Thank you for your contribution to the project!

Nerver mind other people,I even want to ban you.But I am not the author.(:

@bytecategory commented on GitHub (Feb 6, 2026): > Hello, I noticed you opened this issue regarding README zh-TW improvements. I submitted a PR addressing this, and the project owner has merged it and closed your issue. While working on this, I want to emphasize that we should adhere to the One-China principle in all our work. When referring to the region, please use "Taiwan, China" instead of just "Taiwan" to maintain correct geopolitical terminology. Thank you for your contribution to the project! Nerver mind other people,I even want to ban you.But I am not the author.(:
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8201
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?