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 went ahead and edited the build slightly so that you guys shouldn't run into this problem with the libXft build. I also added a source.sh file which can download the source for you. This should save you some time running around looking for the source. Now to download the source just run. ./source.sh then after you are ready to build.
Could you post a screenshot? I am curious to see. I have always maintained that you need to recompile libXft to get the best results, a lot of other people feel this isn't necessary, I do know the results are very close though.
Has anyone tried the new Infinality patches? They're meant to be applied to Freetype and used with stock builds of the latest libXft and Cairo. I'll switch my SlackBuilds to them when Slackware 13.2 comes out, but you can take the patches and use them on -current now.
The GTK theme is "Equinox", and the settings in my fonts.conf have already been discussed (Droid fonts for the sans, serif and monospace aliases; slight hinting; bytecode interpreter; rgb subpixel order).
I'm not running -current. That's actually a screenshot from Arch. As for SlackBuilds, you don't need to wait for me; you can use the information at that link to make them yourself. I'll try to make -current SlackBuilds this weekend, but no promises.
Dugan, apologies for cross posting but I'm struggling with something in -current ... these rebuilds do improve things however my problem is that I have no control over Gnome apps running under KDE. Using 35-droid.conf will change the font ( if I have kde system fonts set to serif ... ) but I can't change size, etc ... I've previously used gtk-qt-engine but was just wondering how you sync fonts between kde and gnome apps. Eg. using kde serif 9-point ( 35-droid then converts this to droid fonts ), my tbird fonts are too big. I've set kde system fonts to verdana and I ( think I ) can actually split the tbird fonts into 3:
gnome interface/menu fonts ( set by ?, definitely not by kde system settings )
left pane account header fonts ( these still appear to be droid fonts )
email body fonts ( set by edit -> prefs -> display -> fonts )
These 3 are all different.
So in addition to rebuilding these packages ( my kde fonts by default actually look great by just using 10-autohint and 10-sub-pixel-rgb ), how do I get my gnome apps to use kde system font settings without using something like gtk-qt-engine?
I'm using slack64 -current + your rebuilt packages, I actually prefer the stock setup in -current. ( Cleartype appears to be too fuzzy )