VS 2022 C# interactive doesn't handle Korean input properly
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the issue in the Visual Studio 2022 C# Interactive window using Korean input, then compare the behavior with Developers PowerShell for Visual Studio. Done means Korean characters are displayed correctly without duplication or splitting; the payload does not identify a source file or test to run.
Written by the indexing model from the issue text.
Description
This issue has been moved from a ticket on Developer Community.
[severity:It bothers me. A fix would be nice]
This report is for Visual Studio(I tried several times to report through VS&installer, but I failed. And It seems I can’t change the tag)
Dear VS Developers,
In VS 2022 17.7.5 interal C# interactive, it seems like Korean language input is not handled properly.
Letters are duplicated and split up as screenshot. When I tried C# interactive in Developers PowerShell for VS 2022, letters were displayed correctly.
Searching this problem, I have found former feedbacks that reported similar problems as below. And it hasn't been actually resolved.
[https://developercommunity.visualstudio.com/t/Typing-korean-strings-in-C-interactive/1331438]
[https://developercommunity.visualstudio.com/t/The-input-of-Korean-languages-need-to-be/306143]
Thank you.
Original Comments
Feedback Bot on 10/22/2023, 07:54 PM:
(private comment, text removed)
sangig yeo on 10/24/2023, 00:18 AM:
(private comment, text removed)
sangig yeo on 10/24/2023, 01:10 AM:
(private comment, text removed)
sangig yeo on 10/26/2023, 05:39 AM:
(private comment, text removed)
Original Solutions
(no solutions)
- Dominant language
- C#
- Stars
- 78
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/interactive-window
-
dotnet/interactive-window#255 · 2 comments · 6 reactions · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
dotnet/interactive-window#230 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#185 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#184 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
dotnet/interactive-window#183 ·
All issues in dotnet/interactive-window
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
MicrosoftLearning/PL-400_Microsoft-Power-Platform-Developer#231 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
joinrpg/joinrpg-net#5313 ·
Maintainers usually reply within 1 day
-
[12.x] FixIncorrectOwnerIdRelationships can delete legitimate library roots when UserView shares the same pathPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day