TrueType font linking does not work

[akritikos]

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

With the following entries under FontLink

Actual behavior

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

[hanubeki]

I think it's the restriction of DirectWrite that doesn't use FontLink.
Maybe related: #1163, #1790, #2664

[DHowett-MSFT]

TryeType font linking isn't going to be supported in anything that isn't GDI.
/dup #2664

[ghost]

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!