Description of problem:
Text is not antialiased. Perhaps a problem with not building with freetype?
Version-Release number of selected component (if applicable):
Always, easily. Winecfg should have antialiased text, based on experience from
building by hand.
I know that this is probably fair low priority, but it would be nice to see
everything in antialiased goodness. It always amused me that I could get nicer
fonts in my Windows apps in Wine than on Windows proper. :)
Installing Firefox, it shows that the only fonts it sees are System, Courier and
MS Sans Serif. It is undoubtly a font issue. On the other hand, the first time
wine started it took a very long time to scan through all the fonts on the
system, so it's not entirely that it can't find any fonts.
This bug will be fixed in the near future... Thanks so for reporting it :)
I'm not sure if I should be asking this here, but how are you currently building
the package? I tried downloading the SRPM, but it's not tagged for x86_64. Do I
just throw in a --target=i386? What about i386 *-devel packages?
Should be fixed in 0.9.11 release... please reopen if you still have problems
Sorry, but I don't seem to see any change here... Tried regenerating .wine by
removing it and re-running wineprefixcreate, but it didn't make any difference
even with 0.9,11... that indeed is strange...
I don't have a clue... could you attach a screenshot (or mail me direct?) thanks
Created attachment 127261 [details]
screenshot of winecfg
Created attachment 127262 [details]
screenshot of firefox
I've just realised that I never said I'm on amd64... but should that even
matter? This also relates to the question about building from src earlier.
No that should indeed not matter... I am on x86_64 myself...
Then may I ask how you are generating the i386 rpms from the srpm posted in the
extras repos? Currently I can't do rpmbuild on them because I don't have i386
Well actually I don't on that box (but you can always use mock for that as
well). I do testbuilds on my i386 and the buildsystem does the same...
Still seeing it with 0.9.12... Am I alone in seeing this?
Appears to be fixed. What changed?
Nothing on my end +)... thanks for the reply.