OpenWF/SpaceNinjaServer
28
29
Fork 34
Code Issues 24 Pull Requests Actions Packages Projects Releases Activity

WIP: chore(webui): update & improve zh #2615

Closed
qingchun wants to merge 1 commits from qingchun/SpaceNinjaServer:update-zh-2 into main
pull from: qingchun/SpaceNinjaServer:update-zh-2
merge into: OpenWF:main
Conversation 19 Commits 1 Files Changed 1 +50 -50
qingchun commented 2025-08-13 09:56:19 -07:00
Contributor
Copy Link
  • Updated and improved some translations
- Updated and improved some translations
qingchun added 1 commit 2025-08-13 09:56:20 -07:00
chore(webui): update & improve zh
All checks were successful
Build / build (pull_request) Successful in 51s
Details
efe78063b4
BanLanGen commented 2025-08-13 10:48:48 -07:00
Contributor
Copy Link

能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧

能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧
e47b57a42e2068e96dd10f0f2b80c454.png
49 KiB
95992e3556303b1b7387540ee0e4110d.png
10 KiB
1ff05a1bbe34f1614315afba7116b0a4.png
106 KiB
e47b57a42e2068e96dd10f0f2b80c454.png 95992e3556303b1b7387540ee0e4110d.png 1ff05a1bbe34f1614315afba7116b0a4.png
qingchun commented 2025-08-13 10:54:41 -07:00
Author
Contributor
Copy Link

能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧

改括号属于符合翻译规范，数字和英文使用半角括号中文使用全角括号。攻击性别那么强

> 能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧 改括号属于符合翻译规范，数字和英文使用半角括号中文使用全角括号。攻击性别那么强
BanLanGen commented 2025-08-13 10:57:12 -07:00
Contributor
Copy Link

能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧

改括号属于符合翻译规范，数字和英文使用半角括号中文使用全角括号。攻击性别那么强
能提交点有用的吗 天天整这点玩意改来改去

> > 能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧 > > 改括号属于符合翻译规范，数字和英文使用半角括号中文使用全角括号。攻击性别那么强 能提交点有用的吗 天天整这点玩意改来改去
qingchun commented 2025-08-13 11:13:43 -07:00
Author
Contributor
Copy Link

能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧

您要不懂翻译规范的话可以去看看vscode和openwebui这2个100k star的大型项目的中文翻译

> 能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧 您要不懂翻译规范的话可以去看看vscode和openwebui这2个100k star的大型项目的中文翻译
qingchun commented 2025-08-13 11:15:55 -07:00
Author
Contributor
Copy Link

能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧

改括号属于符合翻译规范，数字和英文使用半角括号中文使用全角括号。攻击性别那么强
能提交点有用的吗 天天整这点玩意改来改去

更加口语化更直观的翻译不叫有用那什么叫有用？你真的有点莫名奇妙无理取闹了

> > > 能干点正事吗 中文括号改英文括号也得提交？看不懂括号是吧 > > > > 改括号属于符合翻译规范，数字和英文使用半角括号中文使用全角括号。攻击性别那么强 > 能提交点有用的吗 天天整这点玩意改来改去 更加口语化更直观的翻译不叫有用那什么叫有用？你真的有点莫名奇妙无理取闹了
BanLanGen commented 2025-08-13 11:38:25 -07:00
Contributor
Copy Link

你说得对 你懂翻译规范 注册失败 账号已存在？我建议你先重修小学语文

你说得对 你懂翻译规范 注册失败 账号已存在？我建议你先重修小学语文
Image_1755109967958.png
49 KiB
Image_1755109967958.png
Sainan commented 2025-08-14 07:54:53 -07:00
Owner
Copy Link

I'll wait for the poll results on half-width vs full-width brackets in #general-non-english.

I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing.

I'll wait for the poll results on half-width vs full-width brackets in #general-non-english. I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing.
qingchun commented 2025-08-14 09:28:30 -07:00
Author
Contributor
Copy Link

你说得对 你懂翻译规范 注册失败 账号已存在？我建议你先重修小学语文

首先 Registration failed. 直译为 注册失败。，Account already exists? 直译意思为 账号已经存在？，那么为了更加自然我把它转为陈述句，为 该账号已存在。，合起来就是 注册失败。该账号已存在。
那么再从中文说起，注册失败。 符合主谓短语语法，而 该账号已存在。 符合并列复句语法

详细请见
1.主谓短语
2.并列复句
3.列句英语

> 你说得对 你懂翻译规范 注册失败 账号已存在？我建议你先重修小学语文 首先 `Registration failed.` 直译为 `注册失败。`，`Account already exists?` 直译意思为 `账号已经存在？`，那么为了更加自然我把它转为陈述句，为 `该账号已存在。`，合起来就是 `注册失败。该账号已存在。` 那么再从中文说起，`注册失败。` 符合**主谓短语**语法，而 `该账号已存在。` 符合**并列复句**语法 详细请见 1.[主谓短语](https://baike.baidu.com/item/%E4%B8%BB%E8%B0%93%E7%9F%AD%E8%AF%AD) 2.[并列复句](https://baike.baidu.com/item/%E5%B9%B6%E5%88%97%E5%A4%8D%E5%8F%A5) 3.[列句英语](https://context.reverso.net/%E7%BF%BB%E8%AF%91/%E8%8B%B1%E8%AF%AD-%E4%B8%AD%E6%96%87/registration+failed)
qingchun commented 2025-08-14 09:34:40 -07:00
Author
Contributor
Copy Link

I'll wait for the poll results on half-width vs full-width brackets in #general-non-english.

I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing.

I serve as the Chinese translator for a GitHub repository with 100k stars, and I am confident that the translation above is correct and even more natural and readable than the previous version. BanLanGen is completely causing trouble and using verbal insults against me; his statements are entirely illogical. I am truly disappointed. I earnestly request Sainan to assist me, as he is preventing this PR from being merged.

> I'll wait for the poll results on half-width vs full-width brackets in #general-non-english. > > I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing. I serve as the Chinese translator for a GitHub repository with 100k stars, and I am confident that the translation above is correct and even more natural and readable than the previous version. BanLanGen is completely causing trouble and using verbal insults against me; his statements are entirely illogical. I am truly disappointed. I earnestly request Sainan to assist me, as he is preventing this PR from being merged.
qingchun commented 2025-08-14 09:38:19 -07:00
Author
Contributor
Copy Link

I'll wait for the poll results on half-width vs full-width brackets in #general-non-english.

I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing.

I don't use Discord, and I will wait for the community's response. Thank you very much, Sainan.

> I'll wait for the poll results on half-width vs full-width brackets in #general-non-english. > > I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing. I don't use Discord, and I will wait for the community's response. Thank you very much, Sainan.
qingchun commented 2025-08-14 09:51:49 -07:00
Author
Contributor
Copy Link

I'll wait for the poll results on half-width vs full-width brackets in #general-non-english.

I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing.

According to Chinese National Standard GB/T 15834-2011,
Section 4.9 stipulates the use of full-width parentheses.

> I'll wait for the poll results on half-width vs full-width brackets in #general-non-english. > > I myself am conflicted, because when I write Japanese, I use full-width brackets, but a Japanese friend of mine suggests half-width brackets are preferable because of spacing. According to Chinese National Standard [GB/T 15834-2011](https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=22EA6D162E4110E752259661E1A0D0A8), **Section 4.9** stipulates the use of full-width parentheses.
👍 1
BanLanGen commented 2025-08-14 19:10:18 -07:00
Contributor
Copy Link

你做第三方的翻译仅仅关注一些标点符号和所谓的语法？ 盯着一些直译？不考虑实际吗 生命值再生 能量再生 你不觉得别扭吗 游戏里面是意思是能量恢复 生命恢复 你不去完善这些翻译 反而去盯着一堆标点符号很好玩吗

你做第三方的翻译仅仅关注一些标点符号和所谓的语法？ 盯着一些直译？不考虑实际吗 生命值再生 能量再生 你不觉得别扭吗 游戏里面是意思是能量恢复 生命恢复 你不去完善这些翻译 反而去盯着一堆标点符号很好玩吗
BanLanGen commented 2025-08-14 19:15:18 -07:00
Contributor
Copy Link

你做第三方的翻译仅仅关注一些标点符号和所谓的语法？ 盯着一些直译？不考虑实际吗 生命值再生 能量再生 你不觉得别扭吗 游戏里面是意思是能量恢复 生命恢复 你不去完善这些翻译 反而去盯着一堆标点符号很好玩吗
还有解锁剧情的任务 你不觉得容易引起歧义吗 你的翻译标准就是盯着原文 打开谷歌翻译 复制粘贴？

> 你做第三方的翻译仅仅关注一些标点符号和所谓的语法？ 盯着一些直译？不考虑实际吗 生命值再生 能量再生 你不觉得别扭吗 游戏里面是意思是能量恢复 生命恢复 你不去完善这些翻译 反而去盯着一堆标点符号很好玩吗 还有解锁剧情的任务 你不觉得容易引起歧义吗 你的翻译标准就是盯着原文 打开谷歌翻译 复制粘贴？
BanLanGen commented 2025-08-14 19:18:33 -07:00
Contributor
Copy Link

image.pngimage.png 一点实际也不考虑 只管谷歌翻译的对不对是吧

![image.png](/attachments/10652e8f-76af-42dd-ad32-d2f38c9e9db5)![image.png](/attachments/07ac8341-918b-495a-b0ec-d933ca603b94) 一点实际也不考虑 只管谷歌翻译的对不对是吧
image.png
45 KiB
image.png
313 KiB
BanLanGen commented 2025-08-14 19:25:57 -07:00
Contributor
Copy Link

给10万star的仓库做翻译又能怎么样 骨子里透露出来的傲慢 我对你进行侮辱 你从哪看出来的

给10万star的仓库做翻译又能怎么样 骨子里透露出来的傲慢 我对你进行侮辱 你从哪看出来的
fjsdiogjdlskjkl commented 2025-08-15 05:05:49 -07:00
First-time contributor
Copy Link

我觉得在半角括号前加个空格会好一点，至少间距不会像全角括号那么宽。

解锁所有 Captura 场景

这种改动挺好的，增加了可读性

我觉得在半角括号前加个空格会好一点，至少间距不会像全角括号那么宽。 > 解锁所有 Captura 场景 这种改动挺好的，增加了可读性
Sainan changed title from chore(webui): update & improve zh to WIP: chore(webui): update & improve zh 2025-08-15 08:10:17 -07:00
Sainan commented 2025-08-15 08:11:50 -07:00
Owner
Copy Link

Okay, the community has decided in favour of half-width parentheses.

@qingchun At the very least, update this PR to reflect the style the community has voted on.

Okay, the community has decided in favour of half-width parentheses. @qingchun At the very least, update this PR to reflect the style the community has voted on.
qingchun commented 2025-08-15 12:11:36 -07:00
Author
Contributor
Copy Link

If even a grammatically correct translation that complies with national standards cannot be merged, then why were the previous incorrect translations merged? If you do not intend to merge it, please close this PR directly. I will not waste my personal time here anymore, I have explained this clearly enough. Is correcting errors and adhering to standards somehow my fault? Moreover, I have even been subjected to personal insults. I am extremely disappointed.

If even a grammatically correct translation that complies with national standards cannot be merged, then why were the previous incorrect translations merged? If you do not intend to merge it, please close this PR directly. I will not waste my personal time here anymore, I have explained this clearly enough. Is correcting errors and adhering to standards somehow my fault? Moreover, I have even been subjected to personal insults. I am extremely disappointed.
Sainan commented 2025-08-15 12:21:23 -07:00
Owner
Copy Link

Half-width parentheses won the poll 6 to 2. National standards are cool and all, but this isn't formal writing; colloquialisms are totally acceptable, and clearly preferred by the community. Closing the pull request as per your request.

Half-width parentheses won the poll 6 to 2. National standards are cool and all, but this isn't formal writing; colloquialisms are totally acceptable, and clearly preferred by the community. Closing the pull request as per your request.
Sainan closed this pull request 2025-08-15 12:21:25 -07:00
All checks were successful
Build / build (pull_request) Successful in 51s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
An existing implemention is incorrect
dependencies
Pull requests that update a dependency file
documentation
Improvements or additions to documentation
enhancement
New feature or request specific to the emulator
help wanted
Extra attention is needed
improvement
missing data
part of more major rehaul
Can't be worked on right now without merge conflicts later
pr'd for
Soon™
question
Further information is requested
unimplemented
you can do this
Considered easy enough for someone's first PR.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: OpenWF/SpaceNinjaServer#2615
No description provided.
Delete Branch "qingchun/SpaceNinjaServer:update-zh-2"

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?