Translations for zh-CN and zh-TW are very odd

[mikelei8291]

Is there an existing issue for this?

• I have searched the existing issues

Describe the Bug

First, thanks for the great extension. It saved me from the tedious work of writing configuration files manually.

I'm a native speaker of Chinese (both simplified and traditional) and the translations look very odd to me. It translates "Items" to "物品" which is correct literally but not natural in the context of this extension. Usually, "物品" is referred to objects in real life, instead of virtual things in the computer, where "项目" would be more suitable.

Is it translated by machine translators? If so, I could help translating the extension. However, I didn't find any information about how to do it anywhere in this repo, so please point me to the appropriate procedure of improving translations.

Extension Output

Omitted due to not being a bug of the code, but the translations.

Steps To Reproduce

1. Right click on an explorer item
2. Look at the name of the menu item of the extension

Expected Behavior

Translations are natural to native speakers of the language.

Screenshots

No response

Environment

- OS: Windows 10
- Node: 16.17.1
- VSCode: 1.81.1
- npm: not installed (Why asking though? Should add `VSCode` to the template like the above line instead)

Additional Context

No response

[manifestinteractive]

@mikelei8291 any chance you would be willing to submit a PR with the correct translations?

FYI, regarding the Environment stuff, those questions are in there for devs that are working on developing this code. That question is not really for the users of the extension, but for those working on the code for the extension. If they had problems with a build, the version of Node and the version of NPM are not always in sync based on just Node version ( e.g. different people with the exact same version of node can have different versions of npm ).

[mikelei8291]

Sure, I'll try my best to improve the translation and open a PR when finished.

Thanks for clarifying my question regarding the issue template. I totally missed that point cause I was only thinking about users of the extension reporting issues.