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

Many emojis and other non-ascii characters are having troubles to be shown #6352

New Issue
Closed
opened 2026-01-31 00:36:28 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:36:28 +00:00
Owner
Copy Link

Originally created by @AmyrAhmady on GitHub (Feb 9, 2020).

Hello there, today I finally wanted to try new windows terminal, for a project that has emojis in it and I found this terminal very suitable for this, but I'm kinda having some problems with it, Emojis aren't shown as it should, many of them are shown as question marks, some work
but here's the interesting part, if current window gets updated (like resizing it), everything suddenly works and those question marks turn into emojis
here's a GIF to show what I'm currently experiencing:
2

Environment

Microsoft Windows [Version 10.0.18363.592]
Windows Terminal version: Latest from MS Store (0.8.10261.0)

Steps to reproduce

No clue, asked a few friends and some where experiencing the same issue as mine, it's more like default thing for us.

Expected behavior

Showing emojis without any issue

Actual behavior

printing out question marks

Originally created by @AmyrAhmady on GitHub (Feb 9, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> Hello there, today I finally wanted to try new windows terminal, for a project that has emojis in it and I found this terminal very suitable for this, but I'm kinda having some problems with it, Emojis aren't shown as it should, many of them are shown as question marks, some work but here's the interesting part, if current window gets updated (like resizing it), everything suddenly works and those question marks turn into emojis here's a GIF to show what I'm currently experiencing: ![2](https://user-images.githubusercontent.com/34688664/74101277-6ce91100-4b4d-11ea-8226-8e1a0889d283.gif) <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Microsoft Windows [Version 10.0.18363.592] Windows Terminal version: Latest from MS Store (0.8.10261.0) # Steps to reproduce No clue, asked a few friends and some where experiencing the same issue as mine, it's more like default thing for us. <!-- A description of how to trigger this bug. --> # Expected behavior Showing emojis without any issue <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior printing out question marks <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 00:36:28 +00:00
claunia commented 2026-01-31 00:36:28 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 9, 2020):

This sounds like a duplicate of #1503 and/or #529.

@j4james commented on GitHub (Feb 9, 2020): This sounds like a duplicate of #1503 and/or #529.
claunia commented 2026-01-31 00:36:28 +00:00
Author
Owner
Copy Link

@AmyrAhmady commented on GitHub (Feb 9, 2020):

seems like it, this works for me as well :
https://github.com/microsoft/terminal/issues/1503#issuecomment-571154874

@AmyrAhmady commented on GitHub (Feb 9, 2020): seems like it, this works for me as well : https://github.com/microsoft/terminal/issues/1503#issuecomment-571154874
claunia commented 2026-01-31 00:36:29 +00:00
Author
Owner
Copy Link

@theuserbl commented on GitHub (Feb 9, 2020):

It is also interesting, which files are displayed with emojis.

notepad.exe can create text files in "UTF-16 LE" (little endian), "UTF-16 BE" (big endian), "ANSI", "UTF-8" and "UTF-8 with BOM" (with Byte Order Mark).
Only the unicode formats (UTF) can save emojis.

.... Windows PowerShell ... cmd ... Ubuntu 19.10 Terminal .. PowerShell 6.2.4 on Ubuntu
UTF-8 ........... no ...... no .............. yes ................... yes .............
UTF-8 with BOM .. yes ..... no .............. yes ................... yes .............
UTF-16 LE ....... yes ..... yes ............. no .................... yes .............
UTF-16 BE ....... yes ..... no .............. no .................... yes .............

With Ubuntu I don't mean WSL. Its the complete Ubuntu on VirtualBox.

@theuserbl commented on GitHub (Feb 9, 2020): It is also interesting, which files are displayed with emojis. notepad.exe can create text files in "UTF-16 LE" (little endian), "UTF-16 BE" (big endian), "ANSI", "UTF-8" and "UTF-8 with BOM" (with Byte Order Mark). Only the unicode formats (UTF) can save emojis. `.... Windows PowerShell ... cmd ... Ubuntu 19.10 Terminal .. PowerShell 6.2.4 on Ubuntu` `UTF-8 ........... no ...... no .............. yes ................... yes .............` `UTF-8 with BOM .. yes ..... no .............. yes ................... yes .............` `UTF-16 LE ....... yes ..... yes ............. no .................... yes .............` `UTF-16 BE ....... yes ..... no .............. no .................... yes .............` With Ubuntu I don't mean WSL. Its the complete Ubuntu on VirtualBox.
claunia commented 2026-01-31 00:36:29 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 9, 2020):

@theuserbl FYI, you can get better results displaying UTF-8 files in the cmd shell by changing the codepage to UTF-8 (with chcp 65001).

@j4james commented on GitHub (Feb 9, 2020): @theuserbl FYI, you can get better results displaying UTF-8 files in the cmd shell by changing the codepage to UTF-8 (with `chcp 65001`).
claunia commented 2026-01-31 00:36:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 10, 2020):

@cinnamon-msft @miniksa I think for 1.0, we'll need to have a doc that outlines where emoji will and won't work in the Terminal. Like enumerate the fact that the cmd (et. al) cooked read won't support it, but ubuntu/wsl in general will. I think this might help stem the flow of "emoji doesn't work" issues, if we had a doc pointing to various scenarios and why they don't work.

@zadjii-msft commented on GitHub (Feb 10, 2020): @cinnamon-msft @miniksa I think for 1.0, we'll need to have a doc that outlines where emoji will and won't work in the Terminal. Like enumerate the fact that the `cmd` (et. al) cooked read won't support it, but ubuntu/wsl in general will. I think this might help stem the flow of "emoji doesn't work" issues, if we had a doc pointing to various scenarios and _why_ they don't work.
claunia commented 2026-01-31 00:36:29 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 10, 2020):

I'm going to close this one as a /dupe of #1503, which i've renamed to contain a bit more information.

@DHowett-MSFT commented on GitHub (Feb 10, 2020): I'm going to close this one as a /dupe of #1503, which i've renamed to contain a bit more information.
claunia commented 2026-01-31 00:36:29 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 10, 2020):

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!

@ghost commented on GitHub (Feb 10, 2020): 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!
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 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#6352
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?