You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
execute "code . --locale=zh-tw" in command prompt to launch VS Code 1.0 with Chinese Taiwan UI.
press "F1" to show command palette and try to input ">configure".
input Chinese Traditional chars ">設定" instead.
(please refer to my screenshot attached)
result:
No result for searching keywords started from "configure", but searching "設定" worked.
expectation:
"Commands" in command palette should not be localized.
In addition, the issue here is not about the “searchable”. It is how the user input command.
For example, if a user wants to switch to a git branch, he inputs >git: branch in EN locale of VSCode. (and “git branch” in command prompt)
But in zh-tw locale, “>git: branch” command doesn’t work, and user have to input “>git: 分支” instead.
I believe most of the local developers won't use IME to input Chinese characters for command input.
So, I suggest we can support the command in both English and localized string (e.g. Chinese Traditional)
Thanks.
Terry
The text was updated successfully, but these errors were encountered:
Steps to Reproduce:
(please refer to my screenshot attached)
result:
No result for searching keywords started from "configure", but searching "設定" worked.
expectation:
"Commands" in command palette should not be localized.
In addition, the issue here is not about the “searchable”. It is how the user input command.
For example, if a user wants to switch to a git branch, he inputs >git: branch in EN locale of VSCode. (and “git branch” in command prompt)
But in zh-tw locale, “>git: branch” command doesn’t work, and user have to input “>git: 分支” instead.
I believe most of the local developers won't use IME to input Chinese characters for command input.
So, I suggest we can support the command in both English and localized string (e.g. Chinese Traditional)
Thanks.
Terry
The text was updated successfully, but these errors were encountered: