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.
i just compiled gtk+ 2.10.4 and all dependencies (pango 1.14.4, atk 1.12.1, glib2 2.12.3 and cairo 1.2.4) by myself for Slackware-current. All works fine and my main target to compile gimp 2.3.11 with printer support is succeeded.
But now i have no font antialiasing in my gtk2 applications GDK_USE_XFT is set to 1 but nothing helps.
Just a wild guess, but have you (re)installed the FreeType 2.1.9 package that has the ByteCode Interpreter enabled? IIRC, Alien Bob has such a package at his wiki. You also should be able to find the same at linuxpackages.net.
I do not know why PV does not compile FreeType that way. Yeah, I know, there is the potential of patent infringement, but many distro vendors package FreeType with the ByteCode Interpreter enabled and nobody yet has been sued. And this has been going on for years. Basic common law dictates that by allowing this practice to continue for many years that the patent holder (Apple?) is estopped from suing because they have let the practice continue for so many years. That is, the doctrine of estoppel says that the patent holder's own actions prevent them from suing. Just as important, there never was any consensus opinion that enabling that option was indeed a patent infringement, but only speculation.
The fonts display is dramatically improved by using FreeType with the ByteCode Interpreter enabled. Dramatically. When I first started using GNU/Linux I considered abandoning the idea until I discovered this little trick. The font display was noticeably inferior with or without anti-aliasing. This one little change was significant enough to motivate me to stick with GNU/Linux. The first thing I do when I update any X11 packages is immediately reinstall FreeType 2.1.9 with the ByteCode Interpreter enabled.
Regarding the .fonts.conf file in your home directory, you can delete that file if your preferences are the same as those of the global files found in /etc/fonts. I use KDE, but all I have to do is open the KDE control center page for font configuration and KDE generates a local file even if I make no changes. Annoying. I'll guess that GNOME does the same.
Ok,something strange is going on. In my home dir there is a .fonts.conf file
This file is created by the KDE font/antialiasing applet in the KDE Control Center. Unfortunately, its presence breaks the preferences applet in Gnome that performs the same function. Create a directory and move this file (.fonts.conf) inside of it. Then restart Gnome. This should allow you to set the antialiasing properties in Gnome again using preferences-fonts in the Gnome menu.
I use a modified freetype and do not use antialiasing in KDE. When I go to Gnome, I cannot make the fonts antialiased, nor can I change the hinting settings (not that I want to), unless this file (.fonts.conf) is deleted, renamed or moved.
Yet another way Gnome and KDE do not play nice together.
What do you mean by nothing has happened ? When you run it in console or terminal it should display list of font directories it rebuilds caches for. Do you get some error output ?
I mean that after all no antialiasing is there The fc-cache -fv command works fine and print out a list auf directories and font counts.
Now i have reinstalled the FreeType2 package with the bytecode interpreter enabled. The fonts are looking much better now but no antialiasing ...
I moved the .fonts-conf file from my home dir to /etc/fonts as local.conf. It seams to work a little bit. Now, if it set the antialiasing option in local.conf to true there is antialiasing in Firefox (current Slackware package) but not in applications compiled by myself.
Maybe a linked problem? I have searched my system but i have only one GTK2 and FreeType2 installed. Can it be, that my "home build" applications are linked to some other stuff?