Skip to content

Conversation

@kismet-wl
Copy link

Summary of the Pull Request

Improve Simplified Chinese translations to Chinese language conventions

PR Checklist

  • Closes: Link to issue #xxx
  • Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
  • Tests: Added/updated if needed and all pass
  • Localization: All end user facing strings can be localized
  • Dev docs: Added/updated if needed
  • Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Improve Simplified Chinese translations according to Chinese language conventions.

before after
网络终结点 网络端点
跨 OS 文件访问实施 跨系统文件访问
为缓存的即时释放设置为慢速释放和 dropcache 设为 gradual 缓慢释放;设为 dropcache 迅速释放
适用于 Linux 设置的 Windows 子系统 适用于 Linux 的 Windows 子系统设置
······ ······

Validation Steps Performed

I have built and deployed it on my device to check the translations. Here are some of the screenshots:
屏幕截图 2025-11-22 222401
屏幕截图 2025-11-22 222417
屏幕截图 2025-11-22 222431

* fix translations of "MessageConfigExpected" and "MessageConfigUnknownKey"
* fix some expressions
@kismet-wl
Copy link
Author

@microsoft-github-policy-service agree

@benhillis benhillis self-assigned this Nov 26, 2025
@benhillis
Copy link
Member

Thank you, I've followed up with the translation team with this feedback.

@kismet-wl
Copy link
Author

kismet-wl commented Dec 1, 2025

Thank you, I've followed up with the translation team with this feedback.

Hello, thank you for your additional attention. I'm sorry that I didn't make all of the modifications in one commit for not using git and pull requests more skillfully.
I'm also sorry about the small mistake of missing some characters in my translation version.(#13799
<value>仅当 wsl2.networkingMode 设置为镜像(mirrored)时适用。指定 Linux 应用程序可以绑定的端口,这些端口不会 Windows 自动转发或考虑。应采用逗号分隔的列表格式,例如:3000,9000,9090。</value>)
I'm very delighted that some of my contributions could be useful for your localization team and this project. Thank you for your excellent effort, which brings us great work.
But after checking the pull request #13801, maybe there are some other considerations about stability or something else from your localization team, I still have some personal ideas about the translations of some expressions:

  • I think it would be better to translate Pass the remaining command line as-is to 按原样传递剩余的命令行, not 按时传递剩余的命令行. Because the word as-is has the same meaning as 按原样 in Chinese, while the expression 按时 is mainly the translation of on time or timely.
  • I think it would be better to translate Windows Subsystem for Linux Settings to 适用于 Windows 的 Linux 子系统设置 . Because I think the expression Windows Subsystem for Linux (mainly translated as 适用于 Windows 的 Linux 子系统) is a complete description of this kind of Linux system running on Windows system. The Settings (设置) is to modify some behaviors of this subsystem. The subject in the expression 适用于 Linux 设置的 Windows 子系统 is Windows 子系统 in Chinese, which looks a little strange.
  • I think it would be better to translate Usage to 用法 (method of using), not 使用量 (amount of using ). I can find some correct translations of this word, but there are some remaining wrong translations.
  • And the modification of translation I was about to make is 正在导入通讯组 (Importing distribution). It would be better if the 通讯组 is replaced with 分发 or 发行版. The 通讯组 (maybe group of communication?) has nothing to with 分发 (distribution) in Chinese.
  • (Actually, I still have a lot of ideas about Chinese translation, but I'm a little busy at present. There are so many things left for me to learn and master. If it is acceptable to commit like this (pull request from my own fork), I would keep doing so to make this great project more perfect. )

I feel very sorry about my incomplete modifications on localization. If my inexpert actions left more incomplete work to your team, I feel sad about that.
Have a wonderful day!

@benhillis
Copy link
Member

@kismet-wl - thanks for your contributions. These translations are handled by a service that our team doesn't manage directly. I've filed an issue on them to resolve some of the issues you pointed out, which seem to have been incorporated in this PR:
#13802

Unfortunately, we cannot merge this PR because it will just get overwritten the next time the translation pipeline runs. If you have additional feedback on the translations after the above PR, please file a new issue. Thank you for your time in doing this.

@benhillis benhillis closed this Dec 1, 2025
@kismet-wl
Copy link
Author

I understand that this PR would be overwritten the next time, so it won't be merged. Thank you for your effort.
If I file an issue about the translation, what format would you prefer? Would a .patch file highlighting the changes be best, or just some keywords pointing out the specific modifications? I'd like to know how I can reduce the workload for your team while accurately conveying the issues I've found.
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants