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

Sixel image wrong aspect ratio when using certain fonts #22873

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

Originally created by @ZhangTianrong on GitHub (Feb 7, 2025).

Windows Terminal version

1.22.10352.0

Windows build number

10.0.22631.0

Other Software

yazi v25.2.7

Steps to reproduce

See this issue for detailed information and steps to reproduce. Basically, if you set the terminal font to be one with both powerline/nerd and CJK support like Sarasa Term SC Nerd Font or Consolas with Yahei. The image displayed is distorted in Windows Terminal, while no such problem exists in other terminals like iTerm2 or WezTerm when viewing it with a sixel image viewer like yazi or lsix.

Expected Behavior

The aspect ratio of the sixel images should keep consistent with the actual image and has nothing to do with the terminal font.

Image

(I just changed the font without re-running the commands, but the ratio won't be fixed if you re-run it after changing the font.)

Actual Behavior

Image

Originally created by @ZhangTianrong on GitHub (Feb 7, 2025). ### Windows Terminal version 1.22.10352.0 ### Windows build number 10.0.22631.0 ### Other Software yazi v25.2.7 ### Steps to reproduce See [this issue](https://github.com/sxyazi/yazi/issues/2074#issue-2753443430) for detailed information and steps to reproduce. Basically, if you set the terminal font to be one with both powerline/nerd and CJK support like [Sarasa Term SC Nerd Font](https://github.com/laishulu/Sarasa-Term-SC-Nerd) or [Consolas with Yahei](https://github.com/crvdgc/Consolas-with-Yahei). The image displayed is distorted in Windows Terminal, while no such problem exists in other terminals like [iTerm2](https://github.com/gnachman/iTerm2) or [WezTerm](https://github.com/wez/wezterm) when viewing it with a sixel image viewer like [yazi](https://github.com/sxyazi/yazi) or [lsix](https://github.com/hackerb9/lsix). ### Expected Behavior The aspect ratio of the sixel images should keep consistent with the actual image and has nothing to do with the terminal font. ![Image](https://github.com/user-attachments/assets/e9937009-9725-44ff-b2d8-2c0426436804) (I just changed the font without re-running the commands, but the ratio won't be fixed if you re-run it after changing the font.) ### Actual Behavior ![Image](https://github.com/user-attachments/assets/d0d5b868-4365-4f44-99e6-1a9cac0a1906)
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:25:53 +00:00
claunia commented 2026-01-31 08:25:54 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 8, 2025):

I consider @j4james the authoritative voice on this, because he's the most knowledgeable person I know when it comes to terminals. I'm worried I may not correctly convey what I learned from him about sixels, but I believe the following to be correct:

Sixels come from the old DEC terminal times and so it assumes that your terminal has cells that match that old one with its 9:20 or 10:20 = 1:2 aspect ratio respectively. The code for that can be found here: f28f65870a/src/terminal/adapter/SixelParser.cpp (L20-L29)

Most monospace fonts are roughly 1:2, which matches the DEC (and other terminals), and it matches the expected sixel aspect ratio. Your font on the other hand appears to be very narrow which results in that elongated circle. To use sixels, you should use a font that is a bit wider.

Alternatively, you can wait for us to implement alternative image protocols, by subscribing here: #5746
Another option would be for you to modify lsix to stretch the image horizontally before rendering them as sixels (I'm not entirely sure how to do that though).

@lhecker commented on GitHub (Feb 8, 2025): I consider @j4james the authoritative voice on this, because he's the most knowledgeable person I know when it comes to terminals. I'm worried I may not correctly convey what I learned from him about sixels, but I believe the following to be correct: Sixels come from the old DEC terminal times and so it assumes that your terminal has cells that match that old one with its 9:20 or 10:20 = 1:2 aspect ratio respectively. The code for that can be found here: https://github.com/microsoft/terminal/blob/f28f65870a9caeb629498c83efc4ab6992c93bad/src/terminal/adapter/SixelParser.cpp#L20-L29 Most monospace fonts are roughly 1:2, which matches the DEC (and other terminals), and it matches the expected sixel aspect ratio. Your font on the other hand appears to be very narrow which results in that elongated circle. To use sixels, you should use a font that is a bit wider. Alternatively, you can wait for us to implement alternative image protocols, by subscribing here: #5746 Another option would be for you to modify lsix to stretch the image horizontally before rendering them as sixels (I'm not entirely sure how to do that though).
claunia commented 2026-01-31 08:25:54 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 10, 2025):

I'll close this issue for now then.

@lhecker commented on GitHub (Feb 10, 2025): I'll close this issue for now then.
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-Bug 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#22873
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?