https://bugs.winehq.org/show_bug.cgi?id=50896
--- Comment #4 from Rafał Mużyło galtgendo@o2.pl --- Please explain this patch to me, as it seems it wouldn't do the necessary work anyway - at most it would prevent invalid access (I'm not testing it yet, but I'll likely get to it soon).
AFAIU, in wine most of gdiplus is built on top of gdi32. I'm not quite sure what the lib code is doing, but I suspect it simply makes the font from the file available to gdi32 - I'm not sure if wine's gdiplus is able to do that (at least without explicit Replacement key entry for the family (or alternatively a fontconfig substitution) - and that wouldn't do quite what it's supposed to). That would mean that *some* font would be used, perhaps even one having necessary glyphs, but not the one meant to be used, despite being technically available.
So, the only part fixed would be trying to access garbage. A definite step up and an improvement over my incorrect hack, but not full solution yet.
Oh, and if I got that part on current wine code not making font families from PrivateFontCollection available to gdi32, would you point me to the code that does it ?