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

Unicode characters not rendering properly via WSL #452

New Issue
Closed
opened 2026-01-30 21:52:43 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 21:52:43 +00:00
Owner
Copy Link

Originally created by @wkbrd on GitHub (Nov 10, 2018).

Originally assigned to: @adiviness on GitHub.

  • Your Windows build number: 10.0.18277.1000

  • What you're doing and what's happening:
    Attempting to view the contents of a UTF-8 file via WSL does not show the contents of the file.

  1. Create a new file on Linux with UTF-8 characters, such as: 国際
  2. Within WSL, attempt view file using vi. Question mark characters will be shown instead.
  • What's wrong / what should be happening instead:

When using vi, expecting to see 国際. Note this problem reproduces with a local file to WSL as well as over an ssh connection. Characters show properly when using PuTTy.

Originally created by @wkbrd on GitHub (Nov 10, 2018). Originally assigned to: @adiviness on GitHub. * Your Windows build number: 10.0.18277.1000 * What you're doing and what's happening: Attempting to view the contents of a UTF-8 file via WSL does not show the contents of the file. 1. Create a new file on Linux with UTF-8 characters, such as: 国際 2. Within WSL, attempt view file using vi. Question mark characters will be shown instead. * What's wrong / what should be happening instead: When using vi, expecting to see 国際. Note this problem reproduces with a local file to WSL as well as over an ssh connection. Characters show properly when using PuTTy.
claunia added the Product-ConhostArea-RenderingResolution-Duplicate labels 2026-01-30 21:52:43 +00:00
claunia commented 2026-01-30 21:52:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 12, 2018):

Is this unique to WSL, or does this issue also repro in a normal cmd/powershell window?

@zadjii-msft commented on GitHub (Nov 12, 2018): Is this unique to WSL, or does this issue also repro in a normal cmd/powershell window?
claunia commented 2026-01-30 21:52:44 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Nov 12, 2018):

Same behavior in WSL and PowerShell.

image

This is most likely caused by a combination of the following:

  1. The glyph for the characters in question likely not available in the currently selected font (Consolas)
  2. Because Console uses GDI to render text, and since GDI does not support font-fallback (a mechanism for dynamically finding and loading a font that does contain the required glyph), Console is unable to render the requested glyph.

We are very aware of this limitation (e.g. see #190) and are working on a set of changes to remedy this issue in a future OS release.

@bitcrazed commented on GitHub (Nov 12, 2018): Same behavior in WSL and PowerShell. ![image](https://user-images.githubusercontent.com/961950/48375373-9a11ef80-e67c-11e8-863d-1f5f57207799.png) This is most likely caused by a combination of the following: 1. The glyph for the characters in question likely not available in the currently selected font (Consolas) 1. Because Console uses GDI to render text, and since GDI does not support font-fallback (a mechanism for dynamically finding and loading a font that does contain the required glyph), Console is unable to render the requested glyph. We are very aware of this limitation (e.g. see #190) and are working on a set of changes to remedy this issue in a future OS release.
claunia commented 2026-01-30 21:52:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 12, 2018):

I'm going to close this as a dupe of #190 then.

@zadjii-msft commented on GitHub (Nov 12, 2018): I'm going to close this as a dupe of #190 then.
claunia commented 2026-01-30 21:52:45 +00:00
Author
Owner
Copy Link

@willi84 commented on GitHub (Jul 4, 2021):

as a workaround try this:
https://stackoverflow.com/a/68236169
install all the fonts and set up "Dejavu sans mono for powerline"

image

@willi84 commented on GitHub (Jul 4, 2021): as a workaround try this: https://stackoverflow.com/a/68236169 install all the fonts and set up "Dejavu sans mono for powerline" ![image](https://user-images.githubusercontent.com/6207308/124392600-e9f2c880-dcf6-11eb-903f-4bc184ef97e2.png)
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-Rendering Product-Conhost 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#452
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?