On Wed Jul 27 16:27:38 2022 +0000, Paul Gofman wrote:
I didn't see application actually trying to use it, it just loads it along with a bunch of other fonts and breaks with division by zero exception when GetOutlineTextMetrics() is not working (probably just finding the font through some enumeration). My test program tries to load that ttf file and that doesn't work on Windows, my initial understanding was that we shouldn't as well if it breaks things. This ttf apparently can't be used on Windows through Windows functions, if only an app will load and render it directly without using winapi for that. An interesting test case would be to see how some real-life bitmap only or color bitmap only ttf behaves on Windows if it can be loaded, do you have such an example in mind? I was struggling to find one but could not. Maybe such ttf are not supported on Windows at all?
Otherwise, we could probably just try to implement GetOutlineTextMetrics() somehow for bitmap only fonts if we need such fonts supported? And then there are probably more missing bits so that font can be actually rendered through gdi functions.