http://bugs.winehq.org/show_bug.cgi?id=17232
--- Comment #17 from Anastasius Focht focht@gmx.net 2009-04-27 11:44:39 --- Hello,
ok I see it now, the fix for broken Samyak truetype font still lives only in trunk but not in official wintricks release from kegel.com
You might try a newer version from there:
--- snip --- svn export http://winezeug.googlecode.com/svn/trunk/winetricks --- snip ---
--- quote --- So it seems this is no Wine issue after all. But where to report this now? At winetricks, so that they can introduce another dirty hack? I guess so; the fact that fontfix is in there at all tells me that the real upstream for the fonts isn't very likely to fix this issue soon :( --- quote ---
Actually I don't know in detail if the problem is due to M$ way of interpreting truetype/opentype standards (compliancy) or real bugs with the font (header/tables/properties/glyph outlines). Fedora had significant fixes for this font package last year, I don't know about Ubuntu.
I suggest that you add a "HOWTO" section to the appdb entry you manage (http://appdb.winehq.org/objectManager.php?sClass=version&iId=15365) describing all the steps needed to get the app to run. Just something like: "Make sure you install app xxx in clean WINEPREFIX" "use winetricks 'aaa bbb ccc' to install required prerequisites" (and description where to get it) "run the installer" "<additional notes" (like the automatic/manual font fixes needed when encountering this problem) That way people overcome obstacles easier and guesswork is prevented.
People tend to look for "HOWTO" and/or "NOTES" when visiting appdb entry but not study test reports. You put the crucial info in the test report.
If you need examples have a look at the entries I manage (although a bit over-engineered to cover every possible user error) ;-)
You close this bug -> "INVALID" because the problem is not a Wine bug.
Regards