The adobe fonts seem to not be antialiased on my machine but they get autoselected for some websites. I don't see a reason why they need to be pulled in automatically by xorg-server unless the user stricly wants it. It runs fine without that package and much nicer fonts are selected. Sure, might be something else that's broken but I really don't need those fonts installed. Mind to remove the dep? Thanks, Sascha Reproducible: Always Steps to Reproduce: 1. open http://www.golem.de in konqueror-4 2. 3. Actual Results: With media-fonts/font-adobe-75dpi installed, aliased, ugly fonts are selected (all other fonts and most other websites look great)
That's a configuration with either KDE, konqueror or fontconfig. Xorg pulls that font because it still needs it. 1.6 should have no font dependency at all. In the mean time, please get in touch with KDE folks to configure your fonts. Thanks
Kde uses as default Dejavu fonts everywhere (since 4.2.1). So it is just your personal config.
For me this dependency is a real problem, too. When I want to produce a PDF from a DOT graph using GraphViz's dot tool, the fonts are totally awkward and ugly. With the help of some GraphViz devs, I was able to track that problem down to that fontconfig somehow prefers the old media-fonts/font-adobe-75/100dpi bitmap fonts over the antialiased urw-fonts. % fc-match Times imR12-ISO8859-1.pcf.gz: "Times" "Regular" % locate timR12-ISO8859-1.pcf.gz /usr/share/fonts/75dpi/timR12-ISO8859-1.pcf.gz /usr/share/fonts/100dpi/timR12-ISO8859-1.pcf.gz They are owned by the packages media-fonts/font-adobe-100dpi-1.0.1 and media-fonts/font-adobe-75dpi-1.0.1. I've tried clearing and recreating the font cache with "fc-cache -frv", but that makes no difference... When I unmerge and mask those packages the ugly fonts problem goes away and it seems there are no programs which suffer from the deinstall, but portage starts complaining that xorg-x11's deps cannot be resolved. So how do I deal with that problem? Why does fontconfig prefer bitmap fonts over antialiased ones, at least in this case?
(In reply to comment #3) > So how do I deal with that problem? Why does fontconfig prefer bitmap fonts > over antialiased ones, at least in this case? That's a fontconfig configuration issue. The X server has nothing to do with that. Thanks
> That's a fontconfig configuration issue. The X server has nothing to do with > that. Ok, I'll open a new bug for that.
> Ok, I'll open a new bug for that. There is already bug 282151 dealing with the fontconfig issue.
