Allow for the configuration of font fallback

[onceSS]

I am a Chinese developer, sometimes I have to use Chinese, or my Chinese version system will display some prompts in Chinese.

However, this terminal cannot specify multiple fonts in setting, for example: "editor.fontFamily": "DejaVu Sans Mono, Noto Sans CJK SC"(an example from vscode).

I hope this terminal can support multiple fonts setting in the future, thank you.

[phuclv90]

I don't think you need to specify different fonts. Regardless of any locale you use, Chinese characters can always be displayed properly because there are font substitution, font linking and font fallback behind the scenes

[mdtauk]

Fonts in the JSON file could be an array, like with CSS, where if a font is not available, or maybe even per glyph - it goes to the next font listed, and falls back.

[DHowett-MSFT]

This will be part of #1790.

[mariusstrom]

Adding the word fontFace in here to make it easier to find this issue.

[mariusstrom]

It would be nice if VS Code and Terminal were more consistent on configuration parameters as well. This is a bigger problem, but this is a good example: vscode uses fontFamily, Terminal uses fontFace as the configuration parameter.

[tsukumijima]

It's been over a year since this issue was opened. Is there any progress in implementing font fallback?
Even for Japanese users like me, this feature is absolutely necessary.

For example, suppose you want to use Cascadia Code in Windows Terminal. For VS Code, you can specify an alternative font to display characters that Cascadia Code doesn't have.
This is not possible with current Windows Terminal, and characters that are not in Cascadia Code are always displayed in the system font (Yu Gothic UI in Japanese). However, the design of the Yu Gothic UI is thin and condensed (see image), there is too much space between the letters, and the weights do not match. At least I find it hard to see on Windows Terminal.

There are not many fonts for coding that contain Japanese characters. If font fallback is possible, you can easily combine alphabet fonts and Japanese fonts, expanding your font choices.
We hope that this feature will be implemented soon. Thank you.

[zadjii-msft]

Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?

That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️

[guodong2005]

Is there any solution to this problem yet ?
My temporary solution is to merge 2 ttf files.

[microhobby]

This is the only issue that limits me from using Windows Terminal over other solutions now.

[zadjii-msft]

Note

Walkthrough

To do per-glyph (codepoint?) fallback you'd use IDWriteFontFallbackBuilder::AddMapping and use the resulting custom IDWriteFontFallback instead of the current one we get through IDWriteFactory2::GetSystemFontFallback. In other words, we can easily add per-codepoint fallback in the future!

From discussion on #14959, specifically this thread: #14959 (comment)

[xd003]

Why is something as important as this not implemented since 4 yrs, please this is something very barebones on linux if you ask me. I am using a Mono font for my Terminal but i needed to add a secondary font for better glyph/icons support in my prompt which is not possible at the moment

[Jaswir]

@xd003

Can you maybe make a gif of how this works in Linux the font fallback thing?
https://www.screentogif.com/

Having things in Gifs describing the issue helps me.
Maybe it'll help get this solved faster:

[Jaswir]

@mdtauk @onceSS @tsukumijima

So let me get this straight the normal font is Japanese (tsu) / Chinese (once) and it should fall back to English font if not available?

[tsukumijima]

@Jaswir No, it's preferable to initially set a beautiful monospace font for English console and programming tasks, and then render glyphs that are not implemented in that font, like Japanese hiragana and kanji, using a secondary monospace font that supports Japanese.
This is because, unlike fonts for English alphabets, Japanese fonts have a vast number of glyphs, limiting the options available, especially for free fonts.
Furthermore, the design of the English numerals and letters in Japanese fonts may not necessarily be suited for console environments. In other words, there's a need to "use a well-designed English font for English letters and numerals, and choose a Japanese font that stylistically matches that English font for hiragana and kanji".
While fonts that combine reputable open-source English and Japanese fonts like HackGen are available, creating such a composite font oneself is considerably laborious and generally not realistic.

[Jaswir]

@tsukumijima

Okay, so you have two fonts. One for the English alphabet and numbers and one for the Japanese characters? With current terminal you cannot have two fonts?

PS: I can play around a bit with vs code and the fonts and check the differences

[tsukumijima]

@Jaswir What does it mean?
English fonts are fonts such as Source Code Pro, while Japanese fonts (including half-width alphanumeric characters) are Kosugi, etc.
"Kosugi" is a monospaced Japanese font that also includes alphanumeric characters. However, the alphanumeric characters in "Source Code Pro" look better on the terminal.
Therefore, in this example, I think "Source Code Pro" should be used preferentially, and "Kosugi" should be used for the characters not included in "Source Code Pro".

[xd003]

@xd003

Can you maybe make a gif of how this works in Linux the font fallback thing? https://www.screentogif.com/

Having things in Gifs describing the issue helps me. Maybe it'll help get this solved faster:

Sure i can do that, but i am didn't quite understood if you need the part where this feature is coded in all the terminal emulators on linux or where exactly is the font fallback defined ? if you need the code part, sorry you will have to find it yourself on their respective github repos as i am not familiar with their codebase. i am linking github for the most preferred/famous linux terminals here - Konsole, Alacritty, Kitty, wezterm, foot, st. Do note that some of these terminals have windows OS support but their development is majorly focused on catering linux users except maybe just wezterm, it works pretty fine on windows i have heard.
If you were asking where is the font fallback defined by the user, each of the github repo i have linked has their own wiki section, it is defined in the respective config files used by the terminals. For example, kitty's font section here clearly shows how to define font fallback.
Good Luck

[newor0599]

You can try using a nerd font, it contains alot of unicode including chinese character!

[janderssonse]

You can try using a nerd font, it contains alot of unicode including chinese character!

I guess that is precisley one of the many reasons that this issue exists. We would like to be able to have fallback font options, as to avoid using hacks like nerd fonts that are patch on fonts, sometimes with great results. sometimes with alignment issues.

[xd003]

You can try using a nerd font, it contains alot of unicode including chinese character!

I guess that is precisley one of the many reasons this issue exists. We wan't to be able to have fallback font as to avoid using hacks like nerd fonts that are patching a fonts, sometimes with great results. sometimes with alignment issues.

Moreover there are very limited number of fonts available within the Nerd Fonts apart from the occasional alignment issues, its not really a viable option as people think it to be

[abceleung]

+1 to this issue.

Since my choice of font (Sarasa Gothic) does not have a prepatched version with nerd font, I used font-patcher in the official nerd font repo to patch nerd font in manually.

Docker example:
docker run --rm -v ./SarasaFixedSlabHC-TTF-1.0.5/:/in:Z -v ./out:/out:Z -e "PN=10" nerdfonts/patcher --adjust-line-height --careful --complete
(Lower PN if you have a weak PC, otherwise it might use up all your RAM and freeze your computer)

Another option I have considered is to use Wezterm, which is cross platform, has tab support and has nerd font as fallback font by default (so you don't have to patch nerd font by yourself).

[zadjii-msft]

For the subset of this thread that has been following along because they want the Powerline glyphs in their prompt but don't have a font with those glyphs: #16729 added some support for the Terminal drawing some of those glyphs itself, rather than relying on the font. That's available in Canary builds, if folks want to give that a try 😄

(understanding though, that this thread is mostly not about powerline glyphs, and there's still a lot of work to do here)