LinuxQuestions.org Member Success StoriesJust spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here.
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.
As far as the font-spacing issue is concerned it may be your choice of fonts. I always get that result to a greater or lesser degree when I choose a true type font for a terminal rather than a monospace font (console, courier new, courier 10 pitch etc.) My personal pref is for console, which is missing from the misc font folder in slack (and others as well, Debian for example) but can be copied from the /opt/kde/share/fonts folder (that may be off a bit - working from memory here ). Check an earlier post of mine in this thread regarding that issue.
Ya, they do look antialiased, but I can't tell you why for sure. I had an issue in SuSE earlier where Konqueror refused to render non-antialiased for web browsing when everything else was working properly. I finally tried shutting down aa completely everywhere (no point ranges, no hinting) and restarting X and that seemed to help. I was then able to edit my preferences again to include hinting and point ranges without konqueror misbehaving.
Hey dude thanks HEAPS for your help. You have no idea how much of a relief this is for my eyes! Everything worked fine here and I'm lovin my linux even more now - thanks to you :-)
Just a quick question (since I'm exhusted from searching/reading about this) - Certain websites (including this one!) make use of the Courier font (not Courier New). My Fedora uses its own native (Type 1 I think) version of it which looks very distorted. How do I make it use the Windows one? I tried moving the native courier fonts from the /usr/X11R6/lib/X11/fonts/Type1/ to some other backup location and added the windows TTF courier font files to /usr/X11R6/lib/X11/fonts/TTF and ran the proper mkfontscale/mkfontdir/chkfontpath commands, but still no luck.
Basically, what I'm asking is this: How do you make linux take precedence of the windows fonts and ignore its own native versions?
Not certain if this is what you are asking, but depending on the browser, you can specify whether the bowser only uses your fonts or allows documents to use other fonts. You will find this option as a radio button on the same page where you select your font preferences. I prefer to allow documents to use other fonts and, on occasion, these will be fonts that do not render well. Forcing the browser to use my fonts will usually fix this, but these sites are in the minority so I keep my settings the same. I use Arial as my default sans serif font and on many sites this renders too small when used for the smallest fonts (LQ is an example). Allowing sites to use their own fonts produces a better result on most occasions.
The only browser where I cannot find this option is konqueror, but I use this less and less for web browsing anyway.
on my linux, look all distorted. I've provided a screenshot here.
I imagine that this is because my linux is using the Type 1 Courier font, which I believe is located in:
Now, after searching google, I managed to get my hands on the original Windows courier font - COURE.FON. Note that this doesn't have a TTF extension.
My question is, how do I make my linux disregard the Type 1 fonts and use the COURE.FON font instead? Ie - how do I make the standard Courier font look good without having to replace it with the TrueType Courier New font eveywhere?
I don't know if it can. But, if if CAN be done, it would be accomplished perhaps by editing /home/<user>/.font.conf and stipulating that antialiasing be enabled "except" for the fonts arial, tahoma, verdana, helvetica - rather than stipulating a particular font size to be exempt from antialiasing. Then all fonts would be antialiased except the ones you want.
You could start with that and, if you are successful try to narrow it down further.
I have no idea if this would work or not but it came to my mind and I thought I would offer it as a suggestion.
I followed your guide a month or so ago and it worked great, I was finally able to get my fonts setup perfectly.
Today I decided to upgrade with swaret, which included the new KDE 3.4 package. Since I upgraded, my fonts look terrible. I followed through your guide again twice, but no matter what I do, the fonts look very bad.
I have confirmed that i'm running in 96x96 DPI and TTF fonts are properly installed. I have compiled the latest Freetype making sure to enable truetype in the ftoption include file to no avail.
Have you recently upgraded to KDE 3.4? Did you also experience similar problems? Do you know of any way to get it fixed up?
Yes I have, though not with swaret. I rsync current on a local drive and use upgradepkg.
KDE 3.4.0 works fine with my install.
Check Xorg.0.log and make sure that freetype is loading correctly from xorg.conf.
I had this happen with an upgrade of ubuntu from warty to hoary. After checking everything and recompiling freetype and reinstalling fonts, I found that freetype was failing with and error. My solution was to do a clean install using a hoary install disk rather than doing an upgrade.
Not sure if this is your problem or not, but it may be worth a look. A re-install may not have been needed in my case, but was the fastest for me since I am not familiar with debian-like systems.
It does appear that FreeType is loading correctly, I have the following in xorg.conf
and see this in the xorg log:
(II) LoadModule: "freetype"
(II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 6.8.2, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font FreeType
I wonder if it's loading the proper freetype module. The /usr/X11R6/lib/modules/fonts/libfreetype.so file hasn't been modified recently. Shouldn't it be loading from /usr/lib?
This is really excellent and worked really well (Fedora Core 3), apart from the Gnome Terminal window now looks terriable, almost unreadable, but everything else is great. Any ideas how to fix the terminal window?