You are not logged in.

#1 2006-02-01 01:17:24

Gullible Jones
Member
Registered: 2004-12-29
Posts: 4,863

Why does the new fontconfig disable bitmap fonts?

Ya know, guys, some of us still use Artwiz fonts... :?

Offline

#2 2006-02-01 03:32:31

stonecrest
Member
From: Boulder
Registered: 2005-01-22
Posts: 1,190

Re: Why does the new fontconfig disable bitmap fonts?

Then go enable it.


I am a gated community.

Offline

#3 2006-02-01 04:11:30

ozar
Member
From: USA
Registered: 2005-02-18
Posts: 1,686

Re: Why does the new fontconfig disable bitmap fonts?

This is the first time ever I've had good browser fonts in Arch without having to mess with them, so the disabling of the bitmap fonts has been helpful on my end.


oz

Offline

#4 2006-02-01 11:57:30

Gullible Jones
Member
Registered: 2004-12-29
Posts: 4,863

Re: Why does the new fontconfig disable bitmap fonts?

Ahh... I'm thinking in terms of Xorg 7, where you can opt to not install the 100dpi and 75dpi fonts... My bad.

Offline

#5 2006-02-01 13:47:02

elasticdog
Member
From: Washington, USA
Registered: 2005-05-02
Posts: 995
Website

Re: Why does the new fontconfig disable bitmap fonts?

Also breaks <code>terminus</code> in the Terminal, which I believe is a fairly popular font.  Why did the default config change? Check out what I was greeted by after the upgrade (it really doesn't like wide letters):

nobitmapfonts8ai.th.png

Is there anything we have to do aside from deleting <code>/etc/fonts/conf.c/10-nobitmaps.conf</code> and restarting X?

--==EDIT==--
Answered my own question...yes that's all you have to do.  After shot:

bitmapfonts5su.th.png

Offline

#6 2006-02-01 16:45:35

elasticdog
Member
From: Washington, USA
Registered: 2005-05-02
Posts: 995
Website

Re: Why does the new fontconfig disable bitmap fonts?

Looks like the <code>fontconfig</code> package was just updated again (now I'm using version 2.3.2-5), and the technique for disabling/enabling bitmap fonts has changed a bit.  Looks like the <code>README</code> file needs to be updated as well...is that something I should bug report?

Now, there's a file <code>10-bitmaps.conf</code> in the <code>/etc/fonts/conf.d/</code> directory that should be symlinked to whichever option you want.  By default, it is symlinked to <code>no-bitmaps.conf</code> in the same directory.  To enable bitmap fonts, all you have to do is change the symlink:

$ sudo ln -sf yes-bitmaps.conf 10-bitmaps.conf

Hopefully that will help some people straighten their fonts out...

Offline

#7 2006-02-01 18:23:35

JGC
Developer
Registered: 2003-12-03
Posts: 1,664

Re: Why does the new fontconfig disable bitmap fonts?

I put the instructions in the font wiki. The README file shipped with the fontconfig package is the same README file as in the source conf.d directory. Before reading that file, I had no idea how the conf.d directory worked.

The reason for disabling the bitmap fonts is that most apps pick up the ugly ones instead of the scalable ones. Users who insist in using bitmap fonts are free to revert the change, the latest package will keep the change permanent on upgrades, if you follow the right instructions to do so smile

Offline

#8 2006-02-01 19:14:00

ozar
Member
From: USA
Registered: 2005-02-18
Posts: 1,686

Re: Why does the new fontconfig disable bitmap fonts?

JGC wrote:

The reason for disabling the bitmap fonts is that most apps pick up the ugly ones instead of the scalable ones.

Thanks for disabling them, as the bitmapped fonts were looking terrible on my box and have been ever since I started using Arch.

I'm glad they are easy to enable, though, for those that want them.   8)


oz

Offline

#9 2006-02-01 20:33:33

Gullible Jones
Member
Registered: 2004-12-29
Posts: 4,863

Re: Why does the new fontconfig disable bitmap fonts?

The problem here isn't so much bitmap fonts per se, but Xorg's 100dpi and 75dpi bitmap fonts, which are very ugly. Perhaps Xorg (pre 7) can be built so as not to include those fonts, and a separate package made for them, as with Totem and its plugin? Or perhaps there is a way to make truetype fonts preferentially selected over bitmap ones as defaults, unless otherwise specified... This isn't a huge deal, but disabling a whole class of fonts by default seems to me a bit of an ugly solution.

Offline

#10 2006-02-26 14:21:23

dtw
Forum Fellow
From: UK
Registered: 2004-08-03
Posts: 4,439
Website

Re: Why does the new fontconfig disable bitmap fonts?

I had problems with this here.

I use the terminus font and I like it.  What is trade-off of using bitmap fonts to allow using terminus/artwiz?

Offline

#11 2006-02-26 19:35:51

Gullible Jones
Member
Registered: 2004-12-29
Posts: 4,863

Re: Why does the new fontconfig disable bitmap fonts?

You're using Xorg 7 now, so you can just enable bitmap fonts and uninstall xorg-fonts-75dpi and xorg-fonts-100dpi (those are the ugly ones).

Offline

#12 2007-05-02 16:32:17

tier
Member
Registered: 2006-09-29
Posts: 13

Re: Why does the new fontconfig disable bitmap fonts?

Hi. I'd like to ask Gullible how can I enable bitmap fonts in Arch 0.8.
ln -s /etc/fonts/conf.avail/70-yes-bitmaps.conf /etc/fonts/conf.d/70-bitmaps.conf
doesn't work sad

Offline

#13 2007-05-02 20:25:50

JGC
Developer
Registered: 2003-12-03
Posts: 1,664

Re: Why does the new fontconfig disable bitmap fonts?

After symlinking you need to restart the fontconfig-using application. Running applications don't re-read the fontconfig policy on the fly, they only read it at startup.

Offline

Board footer

Powered by FluxBB