dotnet/roslyn

InteliSence character c# not match japanese

Open

#35,188 opened on Apr 22, 2019

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-IDEBugDeveloper CommunityIDE-IntelliSenseTenet-Globalizationhelp wanted

Description

This issue has been moved from https://developercommunity.visualstudio.com/content/problem/519645/intelisence-character-c-not-match-japanese.html VSTS ticketId: 841021 These are the original issue comments:

Visual Studio Feedback System on 4/8/2019, 01:56 AM (14 days ago): We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

k_matsumoto on 4/10/2019, 00:07 AM (12 days ago): Sample Code.//It works normally. int EnblishVariable = 0; //Typing "vari" causes Intellisense to display "EnblishVariable".

//It does not work. int 日本語の変数名 = 0; //Typing "変数名" does not show "日本語の変数名" in Intellisense. //Typing "日本語" causes Intellisense to display "日本語の変数名".

Jane Wu [MSFT] on 4/10/2019, 01:12 AM (12 days ago): Translated from Bing:Sample Code.// It works normally. int EnblishVariable = 0; // Typing "vari" causes Intellisense to display "EnblishVariable". // It does not work. int Japanese variable name = 0; // Typing "variable name" does not show "Japanese variable name" in Intellisense. // Typing "Japanese" causes Intellisense to display "Japanese variable name".

These are the original issue solutions: (no solutions)

Contributor guide

Tech stack
csharp
Domain
developer experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C# knowledgeunderstanding of IntelliSense completion
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the completion matching logic in Roslyn's completion service (e.g., CompletionService or CompletionProvider). The issue reports that prefix matching works for Japanese characters but substring matching does not. Look at how the completion filter compares different substrings of identifier names, specifically string comparison methods like `string.StartsWith` or `string.Contains`. Examine whether culture aware or ordinal comparison is used and if Unicode normalization is applied. Check comments or existing tests related to non ASCII identifier handling.