TrueType font linking does not work #5296

Open
opened 2026-01-31 00:09:57 +00:00 by claunia · 0 comments
Owner

Originally created by @akritikos on GitHub (Nov 29, 2019).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.7.3291.0

Any other software?

Steps to reproduce

  • Add a monospace TrueType font and configure a profile to use it
  • Add a second font and configure it as fallback to the first using font linking
  • Open Windows Terminal
  • Characters are reported as missing despite existing in the fallback font

Expected behavior

Characters rendered using the main font, missing glyphs being rendered from the first font containing it in the FontLink configuration.

Here's a preview on PowerShell Core
image

With the following entries under FontLink
image

Actual behavior

Windows Terminal ignores FontLink configuration and renders characters as missing. Same session as in the expected behavior, using Windows Terminal:
image

Originally created by @akritikos on GitHub (Nov 29, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- 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 ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.7.3291.0 Any other software? ``` # Steps to reproduce - Add a monospace TrueType font and configure a profile to use it - Add a second font and configure it as fallback to the first using font linking - Open Windows Terminal - Characters are reported as missing despite existing in the fallback font # Expected behavior Characters rendered using the main font, missing glyphs being rendered from the first font containing it in the FontLink configuration. Here's a preview on PowerShell Core ![image](https://user-images.githubusercontent.com/1242406/69868224-d0cf9d80-12b1-11ea-8156-3421b190a2fc.png) With the following entries under FontLink ![image](https://user-images.githubusercontent.com/1242406/69868291-fceb1e80-12b1-11ea-90aa-7918447fcdbd.png) # Actual behavior Windows Terminal ignores FontLink configuration and renders characters as missing. Same session as in the expected behavior, using Windows Terminal: ![image](https://user-images.githubusercontent.com/1242406/69868362-2c019000-12b2-11ea-8c5a-72f86223d1c0.png)
claunia added the Resolution-Duplicate label 2026-01-31 00:09:57 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5296