http://bugs.winehq.org/show_bug.cgi?id=10952
Ove Kaaven ovek@arcticnet.no changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |major Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #8 from Ove Kaaven ovek@arcticnet.no 2007-12-29 22:05:10 --- The bug heading is "Wine prefers Marlett". The heading is not "Wine doesn't display Arial". Therefore, the premise of the bug is not invalid. You didn't answer this: "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, why would *you* want to let Wine choose Marlett instead of Arial in this case (which it might, regardless of whether msttcorefonts was installed), knowing that Windows wouldn't do this? Do you *want* to let clear bugs go hidden and unfixed by saying "well, don't do that then", or doing a "the problem doesn't exist, go away" Jedi mind trick? Is that supposed to be how quality assurance works in the FOSS world of "let's get things right under the hood, let's make it solid, let's follow principle of least surprise and make it work on a wide range of systems, because we have no bosses that force us to take shortcuts", that made Linux itself so popular? Alexandre has always had this "get-it-right-at-any-cost" attitude, which we should thus be adhering to here since he's the boss, while your "get-it-working-at-any-cost" attitude would be more appropriate for a commercial product like CodeWeavers CrossOver (and probably work pretty well there - it's just that it's not the same thing).
Yes, definitely, finding where the regression is, and submitting patches, is something that needs to be done in short order, of course, but it's better done with the bug open rather than closed. That's just how bug tracking systems are generally used. Bugs are closed *after* patches are applied, not before. You don't have to be involved in it, either; someone else, who might actually have some interest in this, could do all the work. (Maybe even me, if I find time.) You can just sit back and let it happen. I'll even cloes the bug myself if we find out that fontforge is the problem.
And finally, since you ask, I don't personally have a clue why we need Wine in Debian. I've mentioned Debian's arguments - that you can, in principle, run DFSG-free Win32 software (from SourceForge or whatever) on it. Other than that, well... Do you want me to pull it from Debian? I wouldn't really mind, especially if this is the attitude I get. Should we go to wine-devel and discuss doing so? (Note that even if I do pull it, this bug is still valid. Wine prefers Marlett. You're just hiding it by using msttcorefonts, even on other distros (at least once they upgrade their fontforges). So don't close it before we've come up with a patch or something.)