Comment #25 on issue 18159 by pablo.t89: Chrome doesn't honor fontconfig settings http://code.google.com/p/chromium/issues/detail?id=18159
The problem is that XSETTINGS is very, very primitive compared to fontconfig. What if I want some fonts to be antialiased at some sizes, and monochrome at others? E.g. "webcore" truetype fonts (like Arial, Times New Roman, Verdana, ...) look the best when rendered monochrome at 9-14 pixels, and antialiased otherwise. And anything else looks ugly on my screen, but there is no way to define font substitutes/advanced rules in XSETTINGS. Every modern desktop application respects fontconfig settings; fontconfig is a part of Linux Standard Base. It's going to be a big aesthetical regression, until Chrome respects fontconfig settings or gives some ability to define equally advanced font rendering rules (as in my ~/.fonts.conf). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
