http://bugs.winehq.org/show_bug.cgi?id=13829
--- Comment #12 from Paul "TBBle" Hampson Paul.Hampson@Pobox.com 2009-05-12 09:41:40 --- (In reply to comment #11)
(In reply to comment #10)
Setting up font replacements is trivial as long as you know what font to replace with what.
The problem is with font links as these are not so transparent and depend on the font file name, not only its apparent name.
Good. The other day I submitted a patch to undertake the latter automatically, so with only the former needing to be done by packagers (the trivial part) it all works nicely out of the box.
http://www.winehq.org/pipermail/wine-patches/2009-May/072806.html
This patch went into GIT, should be part of the 1.1.22 release.