On Sat, May 26, 2018 at 06:43:39AM -0700, Nikolay Sivov wrote:
This only works together with patch 4/6, right?
Yes. Some of the fixed tests in 5/6 will fail without 4/6 applied before this one.
What we need to figure out here is which font is picked in NO_VISUAL case, does it change with range locale, or custom collection. Then we can either hardcode it here, or add corresponding char ranges.
Going from memory, it was tahoma in win 10 (without custom collection), but I suspect that comes from the system font collection or system fontfallback object.
I don't know if you'd want to hardcode it here. The fontfallback allows you define a mapping between char ranges and font, so the system's fontfallback would seem like the appropriate place for that.