http://bugs.winehq.org/show_bug.cgi?id=10952
Ove Kaaven ovek@arcticnet.no changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |major
--- Comment #2 from Ove Kaaven ovek@arcticnet.no 2007-12-29 18:54:29 --- That's not helpful. This is a regression that affects the usability of Wine on a free system, and is it not the idea of Wine to be free? I seem to recall something about Wine switching to LGPL for such reasons. (It may or may not be a regression in Wine per se, but it's definitely a regression seriously impairing a fundamental part of Wine, something that is supposed to have worked for years. Which is certainly a major problem. Not a "wishlist item".)
And if you uninstalled Arial from Windows, do you really think Windows would substitute with Marlett instead of, say, Tahoma, or MS Sans Serif, or Bitstream Vera (if you've got that; I do), or whatever else that's at least in a non-symbol character set? What if Microsoft Word opened a document written with the "Dragonmaster" font, and the user didn't have it, would Windows choose Marlett then, or would it prefer a non-symbol font? So, what's better, fixing a deficiency in Wine's font selection algorithm (or maybe in the font itself, if the "this is a symbol font" information is lost, or in fontforge) so that there's a sensible fallback (or maybe even adding font alias configuration to winecfg), or considering an entire, popular distro unsupported, for absolutely no good reason?
(And yeah, I've tried to defend msttcorefonts, but you should have seen the other people's arguments - they say that Wine should remain supported in Debian even without those fonts, because it can still be used to run free Windows applications that aren't written to depend on proprietary fonts, and whatnot...)