First of all, I read the disclaimer on the inofficial pipelight patches for wine. :-) Nonetheless, there's an issue with the patches themselves that could easily be resolved: Compholio's patchset includes replacing Arial by Liberation Sans, a font that doesn't seem to recognize the font smoothing capabilities of wine. Thus, applications using the Arial font will start to look extremely ugly, making the text barely readable on flat screen monitors. According to the upstream discussion I just had, the 'real' Arial would work just fine. The replacement is merely done because of redistribution issues with Microsoft's corefonts package. Since corefonts is available in portage, an easy solution to the problem would be to a) let the wine ebuild depend on media-fonts/corefonts, while the 'pipelight' USE flag is set AND b) not to apply the binary patchset "10-Missing_Fonts" from the compholio patchset. I'll attach a patch to the ebuild that does just that and works fine for me. Any thoughts? Reproducible: Always
Created attachment 377674 [details, diff] wine-1.7.19.ebuild_no_font_replacement.patch
Hi, if you modify the patches, you should also regenerate the patch list by executing ./debian/tools/generate-patchlist.sh > ./patches/patch-list.patch otherwise "wine --patches" shows patches which were not applied during the build. Michael
We've had complaints before about wine pulling in corefonts - some users really don't like non-free fonts on their system. Probably this needs to be controlled by a USE flag.
Thinking a bit further: at runtime, wine should be using Microsoft's Arial if it's available, and if it's not available, falling back to the patched-in Liberation alternative. If this doesn't happen, that would seem to be a bug in the Compholio patchset.
(In reply to Michael Müller from comment #2) > ./debian/tools/generate-patchlist.sh > ./patches/patch-list.patch > > otherwise "wine --patches" shows patches which were not applied during the > build. Thanks for the hint.
(In reply to Alexandre Rostovtsev from comment #3) > We've had complaints before about wine pulling in corefonts - some users > really don't like non-free fonts on their system. Oh, I didn't know that. > Probably this needs to be controlled by a USE flag. That would be a nice option, yes!
(In reply to Alexandre Rostovtsev from comment #4) > Thinking a bit further: at runtime, wine should be using Microsoft's Arial > if it's available, and if it's not available, falling back to the patched-in > Liberation alternative. That sounds reasonable and I'm about to re-open the upstream issue with that observation. So maybe we should first see what upstream has to say to this proposal?
Hi, according to https://bugzilla.redhat.com/show_bug.cgi?id=984230 the missing font smoothing seems to be a 'bug' in the liberation fonts package for versions >= 2.00. I reported this upstream and am just now trying to build wine with a modified patchset that includes Liberation Sans 1.07.3 as Arial replacement, instead of the 2.01 which is used by compholio. If that works it might be the mos elegant solution by means of simplicity. Best, Torsten
I just provided a pull request upstream that replaces Liberation Sans by an older version. For me, this works perfectly and solves all the font smoothing issues without having to resort to corefonts. Since the issue will eventually be resolved upstream, I'm closing this bug. Best, Torsten
