https://bugs.winehq.org/show_bug.cgi?id=20456
--- Comment #55 from Erich E. Hoover erich.e.hoover@gmail.com --- (In reply to Mingye Wang from comment #54)
Zebediah and Erich, was my original comment not clear in understanding what the current approach is? ...
Sorry, I misunderstood what you were trying to say.
Let me make my request more clear: try font-to-font substitution (Replacements, FontLink -- there's no shortage of such systems in Wine) first, something along the lines of: ... If it works, we can talk about how to best deploy it and see if it's too much work for ditching some megabytes of baggage.
Unfortunately, it does not work in several cases we have encountered. Here's an example from when we first encountered some of these issues: https://bugs.winehq.org/show_bug.cgi?id=32323#c3
There are a bunch of programs (a lot of them related to .NET) that don't use the proper font system and actually read the fonts from c:\windows\fonts and decode the name from what is stored in the font. In order to appease these programs we need to provide a proper font with the "correct" name in the font data. We could conceivably create this "on the fly", but that's not particularly easy since we would need to create some mechanism to have a placeholder file and copy the font data and modify the name when it's accessed. We're open to clever ideas though, it would be really nice to fix this a better way.