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

right-click menu in UI needs to be localized #23974

New Issue
Open
opened 2026-01-31 08:57:48 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:57:48 +00:00
Owner
Copy Link

Originally created by @kismet-wl on GitHub (Jan 17, 2026).

Originally assigned to: @DHowett on GitHub.

Windows Terminal version

1.23.13503.0

Windows build number

10.0.26200.0

Other Software

No response

Steps to reproduce

A bug similar to #19444

  1. Change "Language" to another language, "中文(简体)" for example;
  2. Go to the 'Settings' page, select a profile and open the text box. Right-click inside the box to see that the right-click menu has not been localised.
    Image

Expected Behavior

It should be displayed in the language set in "Language".

Actual Behavior

It was displayed in English.

Originally created by @kismet-wl on GitHub (Jan 17, 2026). Originally assigned to: @DHowett on GitHub. ### Windows Terminal version 1.23.13503.0 ### Windows build number 10.0.26200.0 ### Other Software _No response_ ### Steps to reproduce A bug similar to #19444 1. Change "Language" to another language, "中文(简体)" for example; 2. Go to the 'Settings' page, select a profile and open the text box. Right-click inside the box to see that the right-click menu has not been localised. <img width="1730" height="923" alt="Image" src="https://github.com/user-attachments/assets/7d0c7de4-96f3-4899-8c39-7e117c71d394" /> ### Expected Behavior It should be displayed in the language set in "Language". ### Actual Behavior It was displayed in English.
claunia added the Issue-BugProduct-TerminalArea-Localization labels 2026-01-31 08:57:49 +00:00
claunia commented 2026-01-31 08:57:49 +00:00
Author
Owner
Copy Link

@homika482005 commented on GitHub (Jan 19, 2026):

Hi maintainers
I’m a student contributor and I’d like to work on this issue.

I can reproduce the bug on my system and noticed it is similar to #19444.
Before starting implementation, I’d like to confirm:

  • Should the context menu use existing localized resources, or
  • Is a new localization hook required for the settings text box?

Happy to share findings once I investigate further. Thanks!

@homika482005 commented on GitHub (Jan 19, 2026): Hi maintainers I’m a student contributor and I’d like to work on this issue. I can reproduce the bug on my system and noticed it is similar to #19444. Before starting implementation, I’d like to confirm: - Should the context menu use existing localized resources, or - Is a new localization hook required for the settings text box? Happy to share findings once I investigate further. Thanks!
claunia commented 2026-01-31 08:57:50 +00:00
Author
Owner
Copy Link

@kismet-wl commented on GitHub (Jan 19, 2026):

Hi maintainers
I’m a student contributor and I’d like to work on this issue.

I can reproduce the bug on my system and noticed it is similar to #19444.
Before starting implementation, I’d like to confirm:

  • Should the context menu use existing localized resources, or
  • Is a new localization hook required for the settings text box?

Happy to share findings once I investigate further. Thanks!

I'm a student too. I am not a maintainer. Perhaps you could contact the maintainer, @DHowett ?

@kismet-wl commented on GitHub (Jan 19, 2026): > Hi maintainers > I’m a student contributor and I’d like to work on this issue. > > I can reproduce the bug on my system and noticed it is similar to #19444. > Before starting implementation, I’d like to confirm: > - Should the context menu use existing localized resources, or > - Is a new localization hook required for the settings text box? > > Happy to share findings once I investigate further. Thanks! I'm a student too. I am not a maintainer. Perhaps you could contact the maintainer, @DHowett ?
claunia commented 2026-01-31 08:57:50 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 21, 2026):

Whoops. I forgot to include #18908 in version 1.23. Thanks!

@DHowett commented on GitHub (Jan 21, 2026): Whoops. I forgot to include #18908 in version 1.23. Thanks!
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
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#23974
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?