starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

The key shortcut does not work for the Korean version of Windows+X menu. #16870

New Issue
Closed
opened 2026-01-31 05:25:39 +00:00 by claunia · 13 comments
claunia commented 2026-01-31 05:25:39 +00:00
Owner
Copy Link

Originally created by @dh377 on GitHub (Feb 24, 2022).

Windows Terminal version

1.12.10393.0

Windows build number

10.0.22000.0

Other Software

Windows display language setting should be Korean, ko or ko-KR.

Steps to reproduce

  1. Pressing on [Windows Key] + X
  2. Pressing on I (It does not respond)

Expected Behavior

It launches "Windows Terminal".

Actual Behavior

The translation should be Windows 터미널(&I) instead of Windows 터미널 (Shortcut key "(I)" is missing). It is not only missing but also not usable. The terminal is not launched by pressing on the key I on the "Windows+X" menu.

Originally created by @dh377 on GitHub (Feb 24, 2022). ### Windows Terminal version 1.12.10393.0 ### Windows build number 10.0.22000.0 ### Other Software Windows display language setting should be `Korean`, `ko` or `ko-KR`. ### Steps to reproduce 1. Pressing on **`[Windows Key]` + `X`** 2. Pressing on **`I`** (It does not respond) ### Expected Behavior It launches "Windows Terminal". ### Actual Behavior The translation should be `Windows 터미널(&I)` instead of `Windows 터미널` (Shortcut key "(`I`)" is missing). It is not only missing but also not usable. The terminal is not launched by pressing on the key `I` on the "Windows+X" menu.
claunia added the Issue-BugProduct-TerminalTracking-ExternalArea-Localization labels 2026-01-31 05:25:39 +00:00
claunia commented 2026-01-31 05:25:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 24, 2022):

Moved upstream to MSFT:38299837. #11793 was already fixed, but we'll make sure they get Korean fixed too.

@zadjii-msft commented on GitHub (Feb 24, 2022): Moved upstream to MSFT:38299837. #11793 was already fixed, but we'll make sure they get Korean fixed too.
claunia commented 2026-01-31 05:25:40 +00:00
Author
Owner
Copy Link

@lychichem commented on GitHub (Feb 25, 2022):

Chinese version of terminal also need this fix. And I think you need to fully check all the translation if they ignored shortcuts. This always happens if the translators are not familiar to how shortcut works. Just as mentioned by @dani-han , the translator should translate the string and append a (&i), but seems some translator (or a bot) don't know this skill.

@lychichem commented on GitHub (Feb 25, 2022): Chinese version of terminal also need this fix. And I think you need to fully check all the translation if they ignored shortcuts. This always happens if the translators are not familiar to how shortcut works. Just as mentioned by @dani-han , the translator should translate the string and append a (&i), but seems some translator (or a bot) don't know this skill.
claunia commented 2026-01-31 05:25:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 25, 2022):

Don't worry, the internal bug is tracking the Chinese string as well ☺️

@zadjii-msft commented on GitHub (Feb 25, 2022): Don't worry, the internal bug is tracking the Chinese string as well ☺️
claunia commented 2026-01-31 05:25:41 +00:00
Author
Owner
Copy Link

@bzzrak commented on GitHub (May 1, 2022):

Hi, the non-admin terminal in Serbian Cyrillic (sr-cyrl-RS) is underlined, but it doesn't work because Disk Management uses the same letter (the letter И, cyrillic for i). Also File Explorer uses the same letter, that one doesn't work either. I'd appreciate if you could get someone to take a look.
Build 22610

image
@bzzrak commented on GitHub (May 1, 2022): Hi, the non-admin terminal in Serbian Cyrillic (sr-cyrl-RS) is underlined, but it doesn't work because Disk Management uses the same letter (the letter И, cyrillic for i). Also File Explorer uses the same letter, that one doesn't work either. I'd appreciate if you could get someone to take a look. Build 22610 <img width="223" alt="image" src="https://user-images.githubusercontent.com/77467869/166128302-8f5bdf33-994f-4682-b615-01060a8f697d.png">
claunia commented 2026-01-31 05:25:41 +00:00
Author
Owner
Copy Link

@lychichem commented on GitHub (May 1, 2022):

The admin terminal in Simplified Chinese has a underline, but it will never work, as it marks "管". It should be "A"
image
@zadjii-msft

@lychichem commented on GitHub (May 1, 2022): The admin terminal in Simplified Chinese has a underline, but it will never work, as it marks "管". It should be "A" ![image](https://user-images.githubusercontent.com/9316590/166146868-0ed76de2-1225-4c02-8768-e89f4d434b62.png) @zadjii-msft
claunia commented 2026-01-31 05:25:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 5, 2022):

Looking through the comments on various internal threads,

  • Korean seems to be fixed (MSFT:39393763 tracked the upstream bug that claimed it was fixed by the loc team)
  • Chinese is tracked by MSFT:39146564 (Which, through a chain of bugs, lead me to MSFT:39167826. This claims that the string is already fixed in the latest build, but I'm not sure if that shipped yet.)
  • Serbian Cyrillic is tracked in MSFT:39426135
@zadjii-msft commented on GitHub (May 5, 2022): Looking through the comments on various internal threads, * Korean seems to be fixed (MSFT:39393763 tracked the upstream bug that claimed it was fixed by the loc team) * Chinese is tracked by MSFT:39146564 (Which, through a chain of bugs, lead me to MSFT:39167826. This claims that the string is already fixed in the latest build, but I'm not sure if that shipped yet.) * Serbian Cyrillic is tracked in MSFT:39426135
claunia commented 2026-01-31 05:25:42 +00:00
Author
Owner
Copy Link

@lychichem commented on GitHub (Jul 7, 2022):

Looking through the comments on various internal threads,

  • Korean seems to be fixed (MSFT:39393763 tracked the upstream bug that claimed it was fixed by the loc team)
  • Chinese is tracked by MSFT:39146564 (Which, through a chain of bugs, lead me to MSFT:39167826. This claims that the string is already fixed in the latest build, but I'm not sure if that shipped yet.)
  • Serbian Cyrillic is tracked in MSFT:39426135

Sadly, after waiting for 2 months, the issue I mentioned are still not fixed on windows 11 zh-CN 22622.290 with terminal 1.14.1862.0 and language pack 22621.1.1.0. @zadjii-msft
Edit: I can really start Windows Terminal (admin) by typing “管”🤣 Ridiculous though but the "shortcut" worked...

@lychichem commented on GitHub (Jul 7, 2022): > Looking through the comments on various internal threads, > > * Korean seems to be fixed ([MSFT:39393763](https://task.ms/39393763) tracked the upstream bug that claimed it was fixed by the loc team) > * Chinese is tracked by [MSFT:39146564](https://task.ms/39146564) (Which, through a chain of bugs, lead me to [MSFT:39167826](https://task.ms/39167826). This claims that the string is already fixed in the latest build, but I'm not sure if that shipped yet.) > * Serbian Cyrillic is tracked in [MSFT:39426135](https://task.ms/39426135) Sadly, after waiting for 2 months, the issue I mentioned are still not fixed on windows 11 zh-CN 22622.290 with terminal 1.14.1862.0 and language pack 22621.1.1.0. @zadjii-msft Edit: I can really start Windows Terminal (admin) by typing “管”🤣 Ridiculous though but the "shortcut" worked...
claunia commented 2026-01-31 05:25:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 11, 2022):

Coincidentally, the localization team reopened those bugs earlier last week. Apparently the loc files didn't get updated or something. Ultimately, we don't control those resources - we just have to wait until the loc team fixes them 😕

@zadjii-msft commented on GitHub (Jul 11, 2022): Coincidentally, the localization team reopened those bugs earlier last week. Apparently the loc files didn't get updated or something. Ultimately, we don't control those resources - we just have to wait until the loc team fixes them 😕
claunia commented 2026-01-31 05:25:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 13, 2022):

Apparently, this was only fixed in "Win11 build 25159". I have no idea when that'll be available for insiders, or what it's build number will look like in its final form.

@zadjii-msft commented on GitHub (Jul 13, 2022): Apparently, this was only fixed in "Win11 build 25159". I have no idea when that'll be available for insiders, or what it's build number will look like in its final form.
claunia commented 2026-01-31 05:25:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 3, 2022):

For bookkeeping purposes, I'm gonna close this out, since there's nothing else for us to do here. If anyone sees this regress past 25159, then just ping me here and I'll repoen the internal bug with that info. Thanks!

@zadjii-msft commented on GitHub (Aug 3, 2022): For bookkeeping purposes, I'm gonna close this out, since there's nothing else for us to do here. If anyone sees this regress past 25159, then just ping me here and I'll repoen the internal bug with that info. Thanks!
claunia commented 2026-01-31 05:25:43 +00:00
Author
Owner
Copy Link

@bzzrak commented on GitHub (Oct 13, 2022):

I just want to confirm that the issue with Serbian was fixed in a recent update of the language pack (on build 22621). It took a while but thanks!

@bzzrak commented on GitHub (Oct 13, 2022): I just want to confirm that the issue with Serbian was fixed in a recent update of the language pack (on build 22621). It took a while but thanks!
claunia commented 2026-01-31 05:25:43 +00:00
Author
Owner
Copy Link

@lychichem commented on GitHub (Oct 13, 2022):

I just want to confirm that the issue with Serbian was fixed in a recent update of the language pack (on build 22621). It took a while but thanks!

+1, the issue was fixed for Simplified Chinese too.

@lychichem commented on GitHub (Oct 13, 2022): > I just want to confirm that the issue with Serbian was fixed in a recent update of the language pack (on build 22621). It took a while but thanks! +1, the issue was fixed for Simplified Chinese too.
claunia commented 2026-01-31 05:25:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 14, 2023):

Looks like MSFT:39428724 is still open for ko-kr, but that might be out of date.

@zadjii-msft commented on GitHub (Mar 14, 2023): Looks like MSFT:39428724 is still open for ko-kr, but that might be out of date.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Localization Issue-Bug Product-Terminal Tracking-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16870
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?