11 Jan
2022
11 Jan
'22
2:16 p.m.
On 1/11/22 16:56, Dmitry Timoshkov wrote:
Nikolay Sivov nsivov@codeweavers.com wrote:
I don't think we want to test for font name match.
Could you please elaborate?
It's undocumented, could change over time, and it's not something linux/mac users can easily install.
For patch 2/2, it's not clear to me if using exact windows font name is a good idea, choice of characters range is also unclear.
I have a .Net WPF application that does precisely what the test replicates, and expects the exact character being rendered.
Test checks if fallback for 0x25d4 character returns a font that supports this character, that's what a successful result for MapCharacters() is in general. So why [0x2196, 0x2bef] specifically?