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

Add Full Uzbekistan Flag Emoji (🇺🇿) Support in Windows Terminal and Windows Emoji Fonts #23872

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

Originally created by @otabekoff on GitHub (Dec 9, 2025).

Description of the new feature

Currently, the Uzbekistan flag emoji 🇺🇿, which is officially included in the Unicode Standard, does not render correctly in Windows Terminal, CMD, or many parts of the Windows ecosystem due to missing glyph support in the default Windows emoji fonts (such as Segoe UI Emoji) or rendering issues in terminal environments.

This results in the Uzbekistan flag appearing as:

  • an empty box
  • a missing-character symbol
  • or nothing at all

This is disappointing for Uzbek users because Uzbekistan is a Unicode-supported, fully recognized independent country, and its flag should be displayed correctly across Windows environments.

The feature request:
Please add full rendering support for the Uzbekistan flag emoji 🇺🇿 in Windows Terminal and the underlying Windows emoji font stack, so that it displays consistently across CMD, PowerShell, Windows Terminal, Notepad, and all modern Windows applications.

Why this feature is important

  • Ensures full Unicode compliance for all country flags, including Uzbekistan
  • Improves international and multilingual UX across Windows
  • Supports inclusivity for users whose country flags currently fail to render
  • Enhances developer experience in terminals, documentation, and CLI tools where Unicode is heavily used
  • Aligns Windows with Android, iOS, macOS, Linux, and web platforms where 🇺🇿 already renders correctly

Proposed technical implementation details

  • Update Segoe UI Emoji and/or Segoe Color Emoji to include the 🇺🇿 (U+1F1FA U+1F1FF) glyph pair
  • Ensure the updated emoji font is used by Windows Terminal, CMD, and PowerShell
  • Optionally add an automatic fallback to a supported emoji font if the primary one lacks certain country flags
  • Validate rendering in both single-width and double-width environments
  • Include tests for Unicode Regional Indicator Symbols in terminal rendering pipelines
Originally created by @otabekoff on GitHub (Dec 9, 2025). ### Description of the new feature Currently, the Uzbekistan flag emoji **🇺🇿**, which *is officially included in the Unicode Standard*, does not render correctly in Windows Terminal, CMD, or many parts of the Windows ecosystem due to missing glyph support in the default Windows emoji fonts (such as Segoe UI Emoji) or rendering issues in terminal environments. This results in the Uzbekistan flag appearing as: * an empty box * a missing-character symbol * or nothing at all This is disappointing for Uzbek users because Uzbekistan is a Unicode-supported, fully recognized independent country, and its flag should be displayed correctly across Windows environments. **The feature request:** Please add full rendering support for the Uzbekistan flag emoji 🇺🇿 in Windows Terminal and the underlying Windows emoji font stack, so that it displays consistently across CMD, PowerShell, Windows Terminal, Notepad, and all modern Windows applications. ## **Why this feature is important** * Ensures **full Unicode compliance** for all country flags, including Uzbekistan * Improves international and multilingual UX across Windows * Supports inclusivity for users whose country flags currently fail to render * Enhances developer experience in terminals, documentation, and CLI tools where Unicode is heavily used * Aligns Windows with Android, iOS, macOS, Linux, and web platforms where 🇺🇿 already renders correctly ### Proposed technical implementation details * Update **Segoe UI Emoji** and/or **Segoe Color Emoji** to include the 🇺🇿 (U+1F1FA U+1F1FF) glyph pair * Ensure the updated emoji font is used by Windows Terminal, CMD, and PowerShell * Optionally add an automatic fallback to a supported emoji font if the primary one lacks certain country flags * Validate rendering in both single-width and double-width environments * Include tests for Unicode Regional Indicator Symbols in terminal rendering pipelines
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 08:54:51 +00:00
claunia commented 2026-01-31 08:54:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 9, 2025):

Unfortunately, this work is outside the scope of this repository and out of my team's control. The introduction of additional regional indicators of flag tag sequences must be undertaken by the folks in Windows who own Geopolitical compliance.

@DHowett commented on GitHub (Dec 9, 2025): Unfortunately, this work is outside the scope of this repository and out of my team's control. The introduction of additional regional indicators of flag tag sequences must be undertaken by the folks in Windows who own Geopolitical compliance.
claunia commented 2026-01-31 08:54:52 +00:00
Author
Owner
Copy Link

@otabekoff commented on GitHub (Dec 9, 2025):

The introduction of additional regional indicators of flag tag sequences must be undertaken by the folks in Windows who own Geopolitical compliance.

Hi @DHowett,

Thank you so much for taking the time to look into this — I truly appreciate your response.
I wanted to ask if you could please point me to the correct place where I can open an issue about this.

I'm developing multiple apps, and seeing that only my country’s flag behaves incorrectly is becoming quite frustrating. I would really like to report it properly so it can be fixed in the right way.

I suspect this might be related to a font issue, or perhaps something else entirely. I’ve seen the same problem appear in terminal and CMD applications I made as well, which is why I initially mentioned it here. But now I realize this may not actually fall within your or your team’s responsibilities.

I'll wait for your response. Thank you again for your help!

@otabekoff commented on GitHub (Dec 9, 2025): > The introduction of additional regional indicators of flag tag sequences must be undertaken by the folks in Windows who own Geopolitical compliance. Hi @DHowett, Thank you so much for taking the time to look into this — I truly appreciate your response. I wanted to ask if you could please point me to the correct place where I can open an issue about this. I'm developing multiple apps, and seeing that only my country’s flag behaves incorrectly is becoming quite frustrating. I would really like to report it properly so it can be fixed in the right way. I suspect this might be related to a font issue, or perhaps something else entirely. I’ve seen the same problem appear in terminal and CMD applications I made as well, which is why I initially mentioned it here. But now I realize this may not actually fall within your or your team’s responsibilities. I'll wait for your response. Thank you again for your help!
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 Needs-Tag-Fix Needs-Triage
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#23872
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?