My favourite mono/.net application dies with 'Style Regular isn't supported by font Tahoma' in 1.1.28.
I did a git bisect and commit 0b9ba054f6c8a2d96c898e7325087f56a6224644 Author: André Hentschel nerv@dawncrow.de Date: Wed Aug 12 19:19:32 2009 +0200
was the entry that breaks, but just reversing it in 1.1.28 does not fix the problem - i.e. more problematic commits later?; however, replacing the wine-shipped tahoma fonts with those from Vista does cure the problem; so does simply deleting them from $WINEPREFIX/drive_c/windows/fonts (and allow substitution from system fonts happen, I think).
I don't know why a german translation would affect my environment (LANG=en_GB.utf8) and setting LANG=C does not fix the problem.
In any case, the correct fix is probably working out what vista-shipped tahoma does which differs from wine-shipped tahoma? Anybody has any thought on this issue?
On Sun, Aug 23, 2009 at 2:02 PM, Hin-Tak Leunghintak_leung@yahoo.co.uk wrote:
My favourite mono/.net application dies with 'Style Regular isn't supported by font Tahoma' in 1.1.28.
I did a git bisect and commit 0b9ba054f6c8a2d96c898e7325087f56a6224644 Author: André Hentschel nerv@dawncrow.de Date: Wed Aug 12 19:19:32 2009 +0200
was the entry that breaks, but just reversing it in 1.1.28 does not fix the problem - i.e. more problematic commits later?; however, replacing the wine-shipped tahoma fonts with those from Vista does cure the problem; so does simply deleting them from $WINEPREFIX/drive_c/windows/fonts (and allow substitution from system fonts happen, I think).
Sounds like you need to rerun the regression test...Does: $ git reset --hard 0b9ba054f6c8a2d96c898e7325087f56a6224644 && git show 0b9ba054f6c8a2d96c898e7325087f56a6224644 | patch -p1 -R && ./configure && make depend && make
fix it?
--- On Sun, 23/8/09, Austin English austinenglish@gmail.com wrote:
On Sun, Aug 23, 2009 at 2:02 PM, Hin-Tak Leunghintak_leung@yahoo.co.uk wrote:
My favourite mono/.net application dies with 'Style
Regular isn't supported by font Tahoma' in 1.1.28.
I did a git bisect and commit 0b9ba054f6c8a2d96c898e7325087f56a6224644 Author: André Hentschel nerv@dawncrow.de Date: Wed Aug 12 19:19:32 2009 +0200
was the entry that breaks, but just reversing it in
1.1.28 does not fix the problem - i.e. more problematic commits later?; however, replacing the wine-shipped tahoma fonts with those from Vista does cure the problem; so does simply deleting them from $WINEPREFIX/drive_c/windows/fonts (and allow substitution from system fonts happen, I think).
Sounds like you need to rerun the regression test...Does: $ git reset --hard 0b9ba054f6c8a2d96c898e7325087f56a6224644 && git show 0b9ba054f6c8a2d96c898e7325087f56a6224644 | patch -p1 -R && ./configure && make depend && make
fix it?
The result of bisect is apparently real. Ran that, it fixes the problem, then applying the commit, and it breaks:
$ git show 0b9ba054f6c8a2d96c898e7325087f56a6224644 | patch -p1 \ && make clean && ./configure && make depend && make
As I said, another workaround is just copying Vista-shipped tahoma* to windows/fonts , or deleting wine-shipped tahoma* and let substitution from system font happen. It is curious why german translation has effect on english locale.
Le dimanche 23 août 2009 21:02:33, Hin-Tak Leung a écrit :
I don't know why a german translation would affect my environment (LANG=en_GB.utf8) and setting LANG=C does not fix the problem.
I just yesterday found a similar fix for a segfaulting "wine iexplore" on a japanese environment kde. The best I could reach with japanese locale was a "HTML" followed by squares (the one when a glyph is missing) before the segfault - probably japanese localisation of "html rendering disabled". Switching to LC_ALL=C cures the crash.
Originaly, the crash was in WoW launcher (which uses web rendering for part of its window).
--- On Mon, 24/8/09, Vincent Pelletier plr.vincent@gmail.com wrote:
Le dimanche 23 août 2009 21:02:33, Hin-Tak Leung a écrit :
I don't know why a german translation would affect my
environment
(LANG=en_GB.utf8) and setting LANG=C does not fix the
problem.
I just yesterday found a similar fix for a segfaulting "wine iexplore" on a japanese environment kde. The best I could reach with japanese locale was a "HTML" followed by squares (the one when a glyph is missing) before the segfault - probably japanese localisation of "html rendering disabled". Switching to LC_ALL=C cures the crash.
Originaly, the crash was in WoW launcher (which uses web rendering for part of its window).
That's sounds quite similiar to the .NET application I use wine mainly for. It requires native mshtml and shdocvw to work with MS.NET (wine's built-in mshtml/shdocvw causes native gdiplus to fail), and uses Gecko with mono; and on start-up, it also renders a web-page sub-window. My font problem starting with wine 1.1.28 is with Gecko/mono.
I'll give LC_ALL=C a try. wine 1.1.29 shows a different error, but switching to Vista-shipped tahoma*.ttf or removing them altogether (thus using platform font) also make the application continue.
What's the commit/sha1 for the fix you found (if it were posted)?