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

A proper Unicode Font setting #14331

New Issue
Open
opened 2026-01-31 04:07:23 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:07:23 +00:00
Owner
Copy Link

Originally created by @ndrogers on GitHub (Jun 24, 2021).

Description of the new feature/enhancement

I often work with unicode, and as anyone who uses unicode can attest, there aren't many fonts that support really nice unicode glyphs. I have seen the feature request for supporting multiple fonts, as Visual Studio Code does, which allows the user to specify a list of fonts. When a glyph is missing from the first font, VSCode allows missing characters to be rendered using subsequent fonts in the font-family. This feature request has been sitting around for a good few years without movement.

Instead of waiting for that feature to never be implemented, I had an alternative idea that might be an easier fix. I want a second font property in the settings. When there is no glyph available in the primaryFont, the unicodeFont will be used to render the missing glyph.

//settings.json
{

    ...,
    "PrimaryFont": "My Favorite Monospace Font",
    "UnicodeFont": "My Nice Unicode Font",
    ...
}

Alternative approach

You could very well just give me a hotkey to toggle between a primaryFont and secondaryFont so that I can switch when I need to, instead of constantly having to keep my settings file open and manually switch between them.

Originally created by @ndrogers on GitHub (Jun 24, 2021). # Description of the new feature/enhancement I often work with unicode, and as anyone who uses unicode can attest, there aren't many fonts that support really nice unicode glyphs. I have seen the feature request for supporting multiple fonts, as Visual Studio Code does, which allows the user to specify a list of fonts. When a glyph is missing from the first font, VSCode allows missing characters to be rendered using subsequent fonts in the font-family. This feature request has been sitting around for a good few years without movement. **Instead of waiting for that feature to never be implemented**, I had an alternative idea that might be an easier fix. I want a second font property in the settings. When there is no glyph available in the `primaryFont`, the `unicodeFont` will be used to render the missing glyph. ```js //settings.json { ..., "PrimaryFont": "My Favorite Monospace Font", "UnicodeFont": "My Nice Unicode Font", ... } ``` # Alternative approach You could very well just give me a hotkey to toggle between a `primaryFont` and `secondaryFont` so that I can switch when I need to, instead of constantly having to keep my settings file open and manually switch between them.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:07:23 +00:00
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#14331
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?