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

some ligature rendered abnormally #16903

New Issue
Closed
opened 2026-01-31 05:26:45 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 05:26:45 +00:00
Owner
Copy Link

Originally created by @zhang-stephen on GitHub (Mar 1, 2022).

Windows Terminal version

1.13.10395.0(preview)

Windows build number

10.0.19042.1466

Other Software

Something over SSH to CentOS 7.9:

  • neovim 0.6.1
  • tmux 3.1a

Fonts:
FiraCode NF(with windows compatible)

Steps to reproduce

  1. install FiraCode NF follow above link

  2. terminal configuration:

    {
    "protiles": {
         "lists": [
            {
                "adjustIndistinguishableColors": true,
                "antialiasingMode": "cleartype",
                "backgroundImage": null,
                "closeOnExit": "always",
                "colorScheme": "Campbell",
                "commandline": "ssh <username>@<hostname>",
                "name": "<remoteHost>",
                "cursorShape": "underscore",
                "experimental.useAtlasEngine": true,
                "font": {
                    "face": "FiraCode NF",
                    "size": 11
                },
                "guid": "{6c5275a4-b63e-46ce-a2eb-e3ea1f73666f}",
                "hidden": false,
                "historySize": 100001,
                "opacity": 85,
                "padding": "8",
                "useAcrylic": true
            }
        ]
    }
}

  3. print this text on terminal(the logo of neovim in following screenshots):
    test.txt

  4. it could be reproduced under powershell 7 on Windows

Expected Behavior

the true rendering in other terminal:

image
image

Actual Behavior

you can find ligatures not effective in screenshots:

image
image

screenshot of Powershell 7:
image

Originally created by @zhang-stephen on GitHub (Mar 1, 2022). ### Windows Terminal version 1.13.10395.0(preview) ### Windows build number 10.0.19042.1466 ### Other Software Something over SSH to CentOS 7.9: + neovim 0.6.1 + tmux 3.1a Fonts: [FiraCode NF(with windows compatible)](https://github.com/ryanoasis/nerd-fonts/releases/download/v2.1.0/FiraCode.zip) ### Steps to reproduce 1. install FiraCode NF follow above link 2. terminal configuration: ```json { "protiles": { "lists": [ { "adjustIndistinguishableColors": true, "antialiasingMode": "cleartype", "backgroundImage": null, "closeOnExit": "always", "colorScheme": "Campbell", "commandline": "ssh <username>@<hostname>", "name": "<remoteHost>", "cursorShape": "underscore", "experimental.useAtlasEngine": true, "font": { "face": "FiraCode NF", "size": 11 }, "guid": "{6c5275a4-b63e-46ce-a2eb-e3ea1f73666f}", "hidden": false, "historySize": 100001, "opacity": 85, "padding": "8", "useAcrylic": true } ] } } ``` 3. print this text on terminal(the logo of neovim in following screenshots): [test.txt](https://github.com/microsoft/terminal/files/8159332/test.txt) 4. it could be reproduced under powershell 7 on Windows ### Expected Behavior the true rendering in other terminal: ![image](https://user-images.githubusercontent.com/17326718/156116977-a91c3b3e-fad1-49a4-97ed-e3ebdfd00292.png) ![image](https://user-images.githubusercontent.com/17326718/156117002-2b2afd14-5b6d-4133-9250-5e848be84416.png) ### Actual Behavior you can find ligatures not effective in screenshots: ![image](https://user-images.githubusercontent.com/17326718/156116802-7bd54f2e-8791-4b73-9bb3-e5895c40275d.png) ![image](https://user-images.githubusercontent.com/17326718/156116898-bbf7cf40-938b-4961-bc2d-611231573ead.png) screenshot of Powershell 7: ![image](https://user-images.githubusercontent.com/17326718/156120184-b5f1a4e6-7d31-472d-b185-a6ebacc3654b.png)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:26:45 +00:00
claunia commented 2026-01-31 05:26:47 +00:00
Author
Owner
Copy Link

@Finii commented on GitHub (Mar 1, 2022):

I believe this is no bug of Windows Terminal but is related to the used font. The linked font is a rather old variant and there have been several fixes in the glyph sizes in the meanwhile. Will check with a HEAD release of that font.

@Finii commented on GitHub (Mar 1, 2022): I believe this is no bug of `Windows Terminal` but is related to the used font. The linked font is a rather old variant and there have been several fixes in the glyph sizes in the meanwhile. Will check with a HEAD release of that font.
claunia commented 2026-01-31 05:26:47 +00:00
Author
Owner
Copy Link

@Finii commented on GitHub (Mar 1, 2022):

With the HEAD font I can not reproduce the issue (no breaks in horizontal box lines).
https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/FiraCode/Regular/complete/Fira%20Code%20Regular%20Nerd%20Font%20Complete%20Windows%20Compatible.ttf

But then I have not the Powershell window?
Maybe you can give us the NeoVim Ascii Art for a test.

image

@Finii commented on GitHub (Mar 1, 2022): With the HEAD font I can not reproduce the issue (no breaks in horizontal box lines). https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/FiraCode/Regular/complete/Fira%20Code%20Regular%20Nerd%20Font%20Complete%20Windows%20Compatible.ttf But then I have not the Powershell window? Maybe you can give us the NeoVim Ascii Art for a test. ![image](https://user-images.githubusercontent.com/16012374/156155626-aa40f659-34cf-40d9-b6f2-485b24a27ad3.png)
claunia commented 2026-01-31 05:26:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 1, 2022):

This might just be the same thing as #12566. Switch to grayscale antialiasing.

@zadjii-msft commented on GitHub (Mar 1, 2022): This might just be the same thing as #12566. Switch to grayscale antialiasing.
claunia commented 2026-01-31 05:26:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 1, 2022):

Okay, sorry for the brief reply earlier. Looking more carefully, I'm gonna say this is definitely a /dup of #8993. This isn't an issue with ligatures, but rather the way cleartype antialiasing interacts with box drawing characters.

@zadjii-msft commented on GitHub (Mar 1, 2022): Okay, sorry for the brief reply earlier. Looking more carefully, I'm gonna say this is definitely a /dup of #8993. This isn't an issue with _ligatures_, but rather the way cleartype antialiasing interacts with box drawing characters.
claunia commented 2026-01-31 05:26:48 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 1, 2022):

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 (Mar 1, 2022): 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!
claunia commented 2026-01-31 05:26:48 +00:00
Author
Owner
Copy Link

@zhang-stephen commented on GitHub (Mar 1, 2022):

With the HEAD font I can not reproduce the issue (no breaks in horizontal box lines). https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/FiraCode/Regular/complete/Fira%20Code%20Regular%20Nerd%20Font%20Complete%20Windows%20Compatible.ttf

But then I have not the Powershell window? Maybe you can give us the NeoVim Ascii Art for a test.

image

I uploaded the test.txt, includes NeoVim Ascii Art, you can find it in the first issue message. And I will try the HEAD font. thanks.

On the other hand, did you test this issue on stable release? I noticed the page settings is different to preview release.

@zhang-stephen commented on GitHub (Mar 1, 2022): > With the HEAD font I can not reproduce the issue (no breaks in horizontal box lines). https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/FiraCode/Regular/complete/Fira%20Code%20Regular%20Nerd%20Font%20Complete%20Windows%20Compatible.ttf > > But then I have not the Powershell window? Maybe you can give us the NeoVim Ascii Art for a test. > > ![image](https://user-images.githubusercontent.com/16012374/156155626-aa40f659-34cf-40d9-b6f2-485b24a27ad3.png) I uploaded the test.txt, includes NeoVim Ascii Art, you can find it in the first issue message. And I will try the HEAD font. thanks. On the other hand, did you test this issue on stable release? I noticed the page `settings` is different to preview release.
claunia commented 2026-01-31 05:26:48 +00:00
Author
Owner
Copy Link

@zhang-stephen commented on GitHub (Mar 1, 2022):

Okay, sorry for the brief reply earlier. Looking more carefully, I'm gonna say this is definitely a /dup of #8993. This isn't an issue with ligatures, but rather the way cleartype antialiasing interacts with box drawing characters.

I cannot find effective solution in #8993, any suggestions? I came back to the stable release in MS store right now.

@zhang-stephen commented on GitHub (Mar 1, 2022): > Okay, sorry for the brief reply earlier. Looking more carefully, I'm gonna say this is definitely a /dup of #8993. This isn't an issue with _ligatures_, but rather the way cleartype antialiasing interacts with box drawing characters. I cannot find effective solution in #8993, any suggestions? I came back to the stable release in MS store right now.
claunia commented 2026-01-31 05:26:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 1, 2022):

Set "antialiasingMode": "grayscale", in your profile. See https://github.com/microsoft/terminal/issues/8993#issuecomment-903904116

@zadjii-msft commented on GitHub (Mar 1, 2022): Set `"antialiasingMode": "grayscale",` in your profile. See https://github.com/microsoft/terminal/issues/8993#issuecomment-903904116
claunia commented 2026-01-31 05:26:49 +00:00
Author
Owner
Copy Link

@zhang-stephen commented on GitHub (Mar 1, 2022):

Set "antialiasingMode": "grayscale", in your profile. See #8993 (comment)

image

thanks for your reply but it is not effective.

@zhang-stephen commented on GitHub (Mar 1, 2022): > Set `"antialiasingMode": "grayscale",` in your profile. See [#8993 (comment)](https://github.com/microsoft/terminal/issues/8993#issuecomment-903904116) ![image](https://user-images.githubusercontent.com/17326718/156200775-c7656924-20d8-4071-9c5b-4f2e2e35e3a3.png) thanks for your reply but it is not effective.
claunia commented 2026-01-31 05:26:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 1, 2022):

Could you share your settings.json file?

@zadjii-msft commented on GitHub (Mar 1, 2022): Could you share your [settings.json file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file)?
claunia commented 2026-01-31 05:26:50 +00:00
Author
Owner
Copy Link

@zhang-stephen commented on GitHub (Mar 1, 2022):

settings.zip
Github doesn't support to upload .json file.

I think I found the root cause: "experimental.useAtlasEngine": true, . the rendering looks normal after this field disabled and re-opening the terminal, even "antialiasingMode" filled as cleartype, but I don't remember I have turned on it.

Thank you again.

@zhang-stephen commented on GitHub (Mar 1, 2022): [settings.zip](https://github.com/microsoft/terminal/files/8162941/settings.zip) Github doesn't support to upload `.json` file. I think I found the root cause: `"experimental.useAtlasEngine": true, `. the rendering looks normal after this field disabled and re-opening the terminal, even `"antialiasingMode"` filled as `cleartype`, but I don't remember I have turned on it. Thank you again.
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 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#16903
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?