[SOLVED] Strange font rendering in Firefox after latest updates
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Posts: 781
Rep:
Strange font rendering in Firefox after latest updates
Hi all,
Done the latest upgrade, but I am having a strange problem with fonts under Firefox/Seamonkey and Google Chrome.
When displaying web pages, any character with a sloped element to it, i.e. W,X,Z,N.K, or anything circular, (O,0,Q) etc, (but only when in lowercase) , the sloped part looks as though it has missing pixels, and subsequently these letters look 'washed out'.
Also seeing this problem when using native Konqueror, so not sure where to start determining the reason for it.
A lot of font problems were reported with the lastest current updates. It seems these problem may come from the fact that the new freetype package in current has the font byte code interpreter enabled by default. You can either disable the BCI and go back to using the autohinter (see post #9 http://www.linuxquestions.org/questi...s-then-844706/)
I have the same problem on slackware current. This work for me -> System Settings -> Common Apperance and Beavior -> Application Apperance -> Fonts -> Use anti-aliasing : Enabled -> Configure -> Only set Hinting Style to Slight. OK, Apply, and restart X.
I have the same problem on slackware current. This work for me -> System Settings -> Common Apperance and Beavior -> Application Apperance -> Fonts -> Use anti-aliasing : Enabled -> Configure -> Only set Hinting Style to Slight. OK, Apply, and restart X.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
