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.
On my quest to make my fonts (Slackware 12) look better, I've tried my hand on the whole freetype bytecode/subpixel thing. I've downloaded the source and the slackbuild script from ftp.slackware.com and uncommented the two lines described in the slackbuild script.
I've then installed the resulting package and restarted X.
Result: Nothing. Fonts are still looking the same, meaning somewhat "blurry".
Am I missing something? Do I need to adjust any other settings for this package to take effect?
Also I've tried installing the qt-gtk engine so I can control the look of Thunderbird and Firefox, but alas; this doesn't appear to be working either. Both programs look exactly as they've always looked: Blocky and clumsy - no matter how I set the new qt-gtk engine control in the KDE Control Center.
I am interested in this as well, because to my eye I have never got Slackware 12 looking as good as Slackware 11 despite having, as far as I can see near identical set ups regarding fonts. I also have done the bytecode/subpixel thing. It seems to do the trick in Slackware 11 but things do not look quite right to me in 12. This is the main reason why I am sticking with 11 for now.
(I like verdana, choose your preferred font and size - of course microsoft fonts don't come with slackware)
(if you use kde) go to Control centre>fonts and adjust to your liking. I have antialiasing enabled, but then in the configure part, I disable from 8-15 pts
Here's what I did to get the fonts how I like 'em:
1. Installed the bytecode/subpixel enabled freetype package
2. Ran the two font related scripts from setup (pkgtool/setup)
3. Enabled sub pixel hinting in the KDE Control Center (RGB, Full)
4. Restarted X.
Voila! Fonts are now looking great.
A funny thing: I have two systems running side by side. One is equipped with a cheap nVidia graphics card and the other is equipped with an onboard Intel 965 chip.
Prior to installing the nVidia driver, both systems looked the same, but after having installed the nVidia driver the nVidia systems looks a lot better. Everything is more "crisp".
On this post I posted my freetype/cairo/libXft patches that I compiled for the slackware community that adds subpixel support and bytecode interpreter, plus my .fonts.config file. give these post a look and if you have any questions let us know http://www.linuxquestions.org/questi...t-geek-570440/
So basically to summarize... You did the right thing by recompiling freetype with bytecode and sub pixel rendering support, but if you want the most optimal results you need to also recompile Cairo and libXft with the patches that were supplied by david turner of freetype a while back. The patches in question basically make cairo and libXft use the subpixel rendering libraries of freetype. once you have all 3 packages recompiled then you need to make a file called .fonts.conf and put it in your home directory (you can use KDE font settings, but I find it lacking a bit in settings). As I stated above I already recompile all the said packages with patches for everyone in the above post if you want to just use mine instead of recompiling all of it yourself.
DisplaySize width height
This optional entry gives the width and height, in millimetres,
of the picture area of the monitor. If given this is used to
calculate the horizontal and vertical pitch (DPI) of the screen.
so, put in your width and height instead of my numbers there. That really made the fonts a lot clearer ... something to do with DPI.
Good Point, make sure your font DPI is 96x96. You can check this by typing
xdpyinfo | grep resolution
if it isn't you can use the above solution, but lately I just edit /usr/bin/startx and add this line to server arguments (In Red)
#!/bin/sh
# $Xorg: startx.cpp,v 1.3 2000/08/17 19:54:29 cpqbld Exp $
#
# This is just a sample implementation of a slightly less primitive
# interface than xinit. It looks for user .xinitrc and .xserverrc
# files, then system xinitrc and xserverrc files, else lets xinit choose
# its default. The system xinitrc should probably do things like check
# for .Xresources files and merge them in, startup up a window manager,
# and pop a clock and serveral xterms.
#
# Site administrators are STRONGLY urged to write nicer versions.
#
# $XFree86: xc/programs/xinit/startx.cpp,v 3.16tsi Exp $
userclientrc=$HOME/.xinitrc
sysclientrc=/usr/lib/X11/xinit/xinitrc
Daedra, are you aware of any new patches? Last I tried, quite awhile ago, the cairo patch was broken and possibly even libxft.
1.4.6 or maybe even 1.4.4 was the last cairo that patched cleanly.
Yes, but the Cairo patch is being maintained by the PLD guys, the newest version applies cleanly to to Cairo-1.4.10, here is a link to all the most current patches. They all apply cleanly to Cairo/libXft/etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.