You are not logged in.
Hi,
I've recently noticed corrupted "m" and "w" characters in Wine. Does anybody have the same problem ?
Last edited by omer666 (2013-12-19 06:11:52)
Offline
Offline
Yes, and lets make sure we are on the same page with the wine version.
[PACMAN] upgraded wine (1.7.7-1 -> 1.7.8-1) I have x86 system.
Last edited by Kilzool (2013-12-07 18:19:00)
Offline
There was someone else addressing the same problem, it wasn't about wine but firefox and chromium I think. Not sure.
Offline
It seems to be a bug in freetype2 2.5.1. I noticed this sort of things happen when using a font with embedded bitmaps enabled (Monaco in my case).
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
Same here, I' reinstalled allfonts, as mentioned on the wiki, and even created the registry key, but I see the same weird characters you see after the wine upgrade to 1.7.8.
Offline
lib32-freetype2 fixed it.
Offline
lib32-freetype2 fixed it.
lib32-freetype2 didn't fix it, freetype2-2.5.2 did.
Offline
Not really sure, but freetype2 by itsself didn't fix it.
Offline
@Dotslash, yes, it did:
2013-12-04 Werner Lemberg <wl@gnu.org>
[sfnt] Fix handling of embedded bitmap strikes.
This corrects the commit from 2013-11-21. Problem reported by
Andrey Panov <panov@canopus.iacp.dvo.ru>.
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
Sorry to push this topic back up, but I've exactly the same problem (lower-case 'm' & 'w' ) and the provided solutions didn't work.
This happens JUST on 11px font size - and I'm not in Wine (using awm / google-chrome-beta).
Any idea how I can troubleshoot?
Update:
seems like installing ttf-microsoft-tahoma solved the issue (for now).
Last edited by derblub (2013-12-10 23:40:16)
Offline
And the font you are using is…?
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
And the font you are using is…?
the font-stack was:
'lucida grande',tahoma,verdana,arial,sans-serif
I tried all and found the corrupted one was "tahoma", not sure what package caused this issue, but just installing ttf-microsoft-tahoma solved it.
Last edited by derblub (2013-12-10 23:45:00)
Offline
I am still affected by this bug in Windows programes using wine. I use the infinality patchset so for me there was no update of freetype until now... I tried ttf-microsoft-tahoma from AUR as suggested by derblub, but that didn't help.
I guess I'll have to wait until a new infinality patch for freetype gets released -- or are there any other pointers?
Offline
I am still affected by this bug in Windows programes using wine. I use the infinality patchset so for me there was no update of freetype until now... I tried ttf-microsoft-tahoma from AUR as suggested by derblub, but that didn't help.
I guess I'll have to wait until a new infinality patch for freetype gets released -- or are there any other pointers?
I don't use infinality, but I just went nuts and installed all the ttf-microsoft fonts from the AUR. Okay, Arial, Tahoma and Verdana. Solved it for me.
Offline
This has NOT been solved. When using Wine, I still get the corrupted m and w. I have the latest freetype2 version 2.5.2. I did the AUR ttf-microsoft-tahoma . Nothing fixes this.
Is there a way to know what font I am looking at? It would probably be the default system font, which is Tahoma for Windows?
Offline
Well, considering it was on my rig I went on and put the solved tag.
Offline
Hi,
I've recently noticed corrupted "m" and "w" characters in Wine. Does anybody have the same problem ?
same problem for me
Offline