On Fri Feb 28 14:43:47 2025 +0000, Daniel Lehman wrote:
Now that has options
have a preference?
A variant of this second option is to use both names - "Tahoma, Noto Sans"
you mean something like?
/* Latin, Combining Diacritical Marks */ { "0000-007F, 0080-00FF, 0100-017F, 0180-024F, " - "0250-02AF, 02B0-02FF, 0300-036F", L"Tahoma" }, + "0250-02AF, 02B0-02FF, 0300-036F, " + "2000-202E, 2030-206F, 2E00-2E44", L"Tahoma, Noto Sans" }, { "0530-058F, FB10-FB1C", L"Noto Sans Armenian" },
Yes, exactly. Regarding preferred way, if we use Tahoma with additional ranges we'll get null glyphs when we miss some glyph in wine's Tahoma. If we use both names we'll have potentially text switching from one font to another for no obvious reason to the user. If we use Noto Sans for everything, all ranges will work, but this will change default config that we had so far.
Maybe we could use "Noto Sans, Tahoma" instead? Does that make sense? On mac for example you're not going to get Noto Sans semi-automatically.
What is your use case, do you need anything from those ranges or you only need non-null font instance?