SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Upgraded to new versions. It is weird that everything works fine, except Firefox (3.5.6), the fonts like the patches never been applied.
Is anyone having the same problem? I had a rebuilt Firefox 3.5.2 from before I upgraded to the new font packages. After I upgraded the font packages, Firefox's font rendering behavior continued as expected.
Last edited by dugan; 01-04-2010 at 09:07 AM.
Click here to see the post LQ members have rated as the most helpful post in this thread.
I'm using Slackware64-current, so I think Pat's build of Firefox is dynamically linked against cairo instead of the static linking under 32-bit. Everything looks good to me in firefox-3.5.6 now that I've got cairo-1.8.8 patched.
Why is Chrome not showing fonts in a manner similar to Firefox? It defaults to using Arial and Times New Roman, and I've switched it to match what I have in Firefox, but I didn't really see any change.
I just wanted to write that I had never before visited your web page about these fonts and things, so I went and had a look just now. It's nice! Really well written and covers a lot of angles dealing with fonts and monitors and X. Cool, nice work.
I have long ago got my subpixel rendering sorted out, but never yet bothered going into great depth regarding my Slackware fonts (AFAICT they are pretty good anyhow); but it's on my list though of things to do eventually, and I'll be using this thread, and your web page, as a guide/template when I get to it.
When font size ranges from 8 to 14, rendering of language specific fonts seems to be broken. 15 and over - font is ok.
Webcore-fonts installed from Dugan's slackbuild, fontconfig and others compiled Cleartype-style.
I rebuilt your packages for 13.1 on a fresh installation a couple of weeks ago, Dugan, and my fonts didn't seem as clear as they did a couple of months ago on -current. Thanks for the tweak - that made a big difference. One thing you might want to mention is that your addition needs to go between the <fontconfig> . . . </fontconfig> tags, not at the end of the file.
Something else I noticed is that I'm missing some entries in /etc/fonts/conf.avail now. Compared to your post #125, I don't have any 10-hinting-*.conf entries, and I don't have 11-lcd-filter-lcddefault.conf. Your conf.d from post #125 was last edited in 08/09 for Slackware 13.0. Is it still consistent with 13.1?
SpelledJ: Those files are no longer there. I've edited post #125 accordingly.
To tweak further, try putting <edit name="antialias" mode="assign"><bool>true</bool></edit> or <edit name="antialias" mode="assign"><bool>false</bool></edit> between the <match> tags.
Also, I tried Chrome, and I noticed that the fonts in the rendering area look different than the fonts in its menus, with the menu fonts being fuzzier and the website fonts being sharper. This leads me to believe that the settings in Chrome's rendering area are actually hardcoded, and cannot be changed. I do know that this is the case with another program: the Gargoyle Interactive Fiction Interpreter.