Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command palette's camel case matching does not work for non ASCII characters #4691

Closed
Tyriar opened this issue Mar 26, 2016 · 8 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority l10n-platform Localization platform issues (not wrong translations)
Milestone

Comments

@Tyriar
Copy link
Member

Tyriar commented Mar 26, 2016

From @espresso3389 in #4679:

I'm on Windows 10 and the IME is ATOK; a Japanese thirdparty IME.
Even with MS-IME, the behavior is same.
Typing "git: プル" correctly works but doing "git プル" does not work.
The search function does not seem to work with Japanese characters.

eea0c49e-f3a0-11e5-9726-32dff53190f6

Is there an optimization to not recheck characters if the last character is replaced? While not being shown here, Japanese IMEs can also transforms multiple Japanese characters into an even smaller number of characters, by going from English -> Kana -> Kanji.

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug l10n-platform Localization platform issues (not wrong translations) labels Mar 27, 2016
@Tyriar
Copy link
Member Author

Tyriar commented Mar 28, 2016

@mysticatea ran into this issue too:

c4e20786-f480-11e5-852c-4a46e97ff853

@Tyriar Tyriar added the important Issue identified as high-priority label Mar 28, 2016
@dbaeumer dbaeumer assigned bpasero and unassigned dbaeumer Mar 29, 2016
@dbaeumer dbaeumer added the candidate Issue identified as probable candidate for fixing in the next release label Mar 29, 2016
@dbaeumer
Copy link
Member

@bpasero assigning to you since this is quick box related. Marking as candidate since we should look into fixing this for 1.0. Let me know if there is something I can do from the translation side.

@bpasero bpasero added this to the April 2016 milestone Mar 29, 2016
@bpasero bpasero changed the title Command palette doesn't support Japanese IME Command palette's camel case matching does not work for non ASCII characters Mar 29, 2016
@bpasero
Copy link
Member

bpasero commented Mar 29, 2016

Looked into this and I think the issue is not about finding Japanese input in general but rather how the filtering works in the command palette. There are different matchers being used and one of them is a camel case matcher that would match for a given input of git pull on Git: Pull only because we think Git: Pull is a valid camel case word with G and P. This however is not the case when using Japanese labels because our check for camel case only considers ASCII characters.

Matching on camel case in the command palette is questionable and should probably be revisited. I quickly checked to use another matcher approach with fully fuzzy matching (similar to files) and could not reproduce the issue there. However, changing our filtering for commands like that can have quite an impact and we also need to revisit the sorting in that case.

I would not do this for GA, but @egamma and @chrisdias should speak up.

@egamma egamma removed the candidate Issue identified as probable candidate for fixing in the next release label Mar 29, 2016
@egamma
Copy link
Member

egamma commented Mar 29, 2016

makes sense

@bpasero
Copy link
Member

bpasero commented Mar 30, 2016

Related: #1964

@Tyriar
Copy link
Member Author

Tyriar commented Mar 30, 2016

Another user who wants either English back or supports English in addition to their native language. #4785

How can i switch back to the English commands or the console can support both 'English' and 'Chinese'?When i'm coding, I have to switch the IME.

67cf555e-f664-11e5-9c1d-072d51adf8d0

753ae82a-f664-11e5-8968-a89819e031ac

@bpasero
Copy link
Member

bpasero commented Mar 31, 2016

I changed our matching in the commands quick open to also match non-ascii beginning of words. This is not yet fuzzy matching, but returns a lot more results that make sense.

Basically the matching is now supporting any beginning of a word (e.g. "gp" matches "Git: Pull" as well as "g p" does).

@bpasero
Copy link
Member

bpasero commented Apr 21, 2016

A fix has landed in insiders. You can give it a try from our insiders release today: http://code.visualstudio.com/Download#insiders

Happy for feedback!

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority l10n-platform Localization platform issues (not wrong translations)
Projects
None yet
Development

No branches or pull requests

4 participants