Slackware 11, I *had* the X fonts in KDE very nice.

Set it up with recompiled for/with the bytecode interpreter enabled. 96 x 96 dpi

Now the X (desktop and KDE apps) it's significantly less noticeable in Firefox -- are rather jagged and rough looking, chunky jagged rough appearing (borked).

How I borked it:

began fiddling with the dpi (not yet borked I don't think).

In KDE control center, clicked to the "defaults" button (now it's borked I think).
--

Restored a backed up copy of my xorg.config (didn't fix).

It's a pentium III with a serverworks chipset with onboard ATI pci video

using native ati module in xorg.

Fonts *were* so superb. How, what I might try to get it back good like it was?

--
Alan.

can you post a screen shot? also font are a very subjective topic on here because there are many different ways you can render your fonts. here is a pic of how I like mine. Also do you have a CRT or a LCD monitor

http://webpages.charter.net/daedra/screen1.png

c (third url) has kmail and kate editor. You can see the uneven in the fonts (bolder, lighter etc.) Not roundness in the C's and O's

It was way better than this, very smooth and even (without the bolder, lighter).

First time in a while I've uploaded to my tripod site. I see they're now more pernicious with popups than they used to be.

My sbc--yahoo internet (ISP) only has pic place and to use it *must* be running silly Win and *must* download and install their silly Win software. I'll not. It's Linux for me.

--
Alan.

Oop.

CRT

Viewsonic A90f+

19 inch

1024 x 768

I think I told it 16 bit for the color depth during config ie xorgconfig

--
Alan.

oh, I forgot to ask, after you enabled the bytecode interpreter did you install the windows core fonts? Arial, Times New Roman, etc. because you have to remember that the bytecode interpreter is only useful for fonts that have the bytecode information such as the windows core fonts?

alias lsg='ls | grep'

al@p3srv:/var/log/packages$ lsg ttf
dejavu-ttf-2.10-noarch-1
ttf-indic-fonts-0.4.7.1-noarch-1
al@p3srv:/var/log/packages$ lsg web
core_web_fonts-20050922-noarch-1rsa

http://www.linuxpackages.net/pkg_details.php?id=9788

That core_web_fonts is part of the original setup, yes.

Installed cab extract from there, then the core web fonts.

I don't know what to look for. I think it happened when I clicked defaults for fonts in kde control center.

I can post screen shots from Slack 11.0 on another box that is without this problem. It looks like this box used to before I borked it on this box.

--
Alan.

well I was thinking of some other options to get the fonts to look good for you with bytecode interpreter, but if you want it like it was all you have to do is reinstall the original freetype package that came with slackware, you can get it off the slackware disk or you can download it directly from here
ftp://ftp.slackware.com/pub/slackwar...1.9-i486-1.tgz

now once its downloaded uninstall the new one like this

removepkg freetype

then install the new package with

installpkg *.tgz

It formerly had smooth, even, very nice fonts, using/with the bytecode interpreter.

So I don't follow about removing the bytecode unless it's due to a misunderstanding.

Thanks.

It must be a setting in a config file somewhere. Or perhaps I need to run like font_fc.cache or whatever, some of those thingys.

I wish I'd previously done disk and/or partition imaged so that I could restore the image. And/or if I knew enough specific to font, I'd have backed up each and every font config file before I began experimenting. As it was, I only backed up xorg.config

Is there somewhere that it lists locations and names of all files having to do with font config?

--
Alan.

/etc/fonts/font.conf

Got my fonts back. Um I'd forgotten that, in the kde control center on two different Slackware 11 boxes, I'd changed it away from the default font settings (did my own custom settings).

After all of this and only recently (Doh!) it occurred to me I might try looking at the font settings in kde control center on the *other* (box # 2 with still ok fonts) box.

Sure enough, set to use different fonts. And the anti-aliasing setting was different too.

So, in conrol center on box # 1, I merely replicate the settings of box # 2. And, voilla, my fonts are back!

So it now appears to me that when I'd clicked and applied the "defaults" for fonts that it had set a not so friendly font for byte code interpreter enabled.

I Won't be clicking and applying that defaults button anytime soon.

*Now* what I'd like to know is what config file(s) do I back up that hold/save these kde control center font settings?

--
Alan.

(where/what are the config files that contain the settings for fonts as set by a user in/using the kde control center)

Since was set by me a user -- it looks like the next 2. the next 2 config files *does* match what I see in the kde control center for the font settings:

al@p3srv:~$ pwd
/home/al
al@p3srv:~$

al@p3srv:~$ cat .fonts.conf
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font" >
<edit mode="assign" name="rgba" >
<const>none</const>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="hinting" >
<bool>true</bool>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="hintstyle" >
<const>hintmedium</const>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="antialias" >
<bool>true</bool>
</edit>
</match>
</fontconfig>
al@p3srv:~$
al@p3srv:~$
al@p3srv:~$ cat .kderc
[General]
StandardFont=Sans Serif,10,-1,5,50,0,0,0,0,0
activeFont=Sans Serif,9,-1,5,75,0,0,0,0,0
background=239,239,239
fixed=Monospace,10,-1,5,50,0,0,0,0,0
font=Sans Serif,10,-1,5,50,0,0,0,0,0
foreground=0,0,0
menuFont=Sans Serif,10,-1,5,50,0,0,0,0,0
selectBackground=103,141,178
selectForeground=255,255,255
taskbarFont=Sans Serif,10,-1,5,50,0,0,0,0,0
toolBarFont=Sans Serif,10,-1,5,50,0,0,0,0,0
windowBackground=255,255,255
windowForeground=0,0,0
al@p3srv:~$

--
Alan.