Fallback font issues?
Posted: Sat Sep 26, 2015 12:47 pm
Scrivener does something weird with fallback fonts in Windows 10 (maybe it always did...)
So, what happens is, if you pick a font that does not have a particular character, scrivener seems to go to your list of fonts and finds the first one in the ALPHABETIC list that contains the character, to replace it.
And the first font in that alphabetic list, is usually some terrible, unreadable, signage style font.
I tried to use Noto Sans (the google font family that contains, in theory, all unicode characters) but it looks like Scrivener actually look into that same font series to find a replacement, and defaults to whatever font shows up first.
So, what happens is, if you pick a font that does not have a particular character, scrivener seems to go to your list of fonts and finds the first one in the ALPHABETIC list that contains the character, to replace it.
And the first font in that alphabetic list, is usually some terrible, unreadable, signage style font.
I tried to use Noto Sans (the google font family that contains, in theory, all unicode characters) but it looks like Scrivener actually look into that same font series to find a replacement, and defaults to whatever font shows up first.