starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Non-US English support #22662

New Issue
Closed
opened 2026-01-31 08:19:49 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:19:49 +00:00
Owner
Copy Link

Originally created by @unknownconstant on GitHub (Dec 12, 2024).

Description of the new feature

The software should use the system language, otherwise use any override in settings.json. The docs currently say language “ Accepts: A BCP-47 language tag like "en-US"” which indicates, to me, arbitrary/ broad language support.

Unfortunately, at present, changing “language” in settings.json to non-American English variants such as “en”, “en-GB”, “enGB”, “en-AU”, “en-CA”, “en-BZ”, “en-IE”, “en-NZ” etc. doesn’t change the language, it remains fixed to “en-US”. Words such as ‘colour/color’ are spelled using the American variant.

It’s probably not something exciting to prioritise but a little goes a long way in terms of making people feel welcome using your product. Given the languages are so similar, the lack of translations feels dismissive. It seems a little ironic for a product which is meant to improve the shell user experience on Windows.

Other languages are installed. French works, but it seems a bit extreme to use a completely different language just to have a locale ‘correct’ spelling.

Proposed technical implementation details

A separate language file - replace American spellings with their non-American counterparts. The languages are similar enough this must be easy to automate. Use AI even. It’s a great buzzword for a write up & performance review.

If it’s not possible to translate, could you adopt a neutral policy instead? I.e. Avoid Noah Webster’s opinions altogether and just have ‘appearance’ instead of ‘color pallet’?

Originally created by @unknownconstant on GitHub (Dec 12, 2024). ### Description of the new feature The software should use the system language, otherwise use any override in settings.json. The docs currently say language “ Accepts: A BCP-47 language tag like "en-US"” which indicates, to me, arbitrary/ broad language support. Unfortunately, at present, changing “language” in settings.json to non-American English variants such as “en”, “en-GB”, “enGB”, “en-AU”, “en-CA”, “en-BZ”, “en-IE”, “en-NZ” etc. doesn’t change the language, it remains fixed to “en-US”. Words such as ‘colour/color’ are spelled using the American variant. It’s probably not something exciting to prioritise but a little goes a long way in terms of making people feel welcome using your product. Given the languages are so similar, the lack of translations feels dismissive. It seems a little ironic for a product which is meant to improve the shell user experience on Windows. Other languages are installed. French works, but it seems a bit extreme to use a completely different language just to have a locale ‘correct’ spelling. ### Proposed technical implementation details A separate language file - replace American spellings with their non-American counterparts. The languages are similar enough this must be easy to automate. Use AI even. It’s a great buzzword for a write up & performance review. If it’s not possible to translate, could you adopt a neutral policy instead? I.e. Avoid Noah Webster’s opinions altogether and just have ‘appearance’ instead of ‘color pallet’?
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 08:19:49 +00:00
claunia commented 2026-01-31 08:19:50 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 8, 2025):

Thanks for filing! I'm going to mark this as a /dup of #10667

@carlos-zamora commented on GitHub (Jan 8, 2025): Thanks for filing! I'm going to mark this as a /dup of #10667
claunia commented 2026-01-31 08:19:50 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jan 8, 2025):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Jan 8, 2025): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Issue-Feature Resolution-Duplicate
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#22662
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?