On 5/3/06, Archaic <[EMAIL PROTECTED]> wrote:
On Wed, May 03, 2006 at 01:32:49PM -0700, Dan Nicholson wrote:
>
> I didn't fully proofread yet, but I think it looks great so far. And
> you got the ed dependency in. Awesome.
Perhaps what ever needs ed can be converted to sed? It's getting to the
point where only gray beards remember how to use ed. I'm really
surprised xorg-7 requires it.
I forgot about that. I'll test that out real soon.
"When installing X, symlinks were created from the OTF and TTF X font
directories to /usr/share/fonts/X11-{OTF,TTF}. This prevents Fontconfig
from using the poorly rendered Type1 fonts or the non-scalable bitmapped
fonts."
We don't symlink to avoid conflict with Fontconfig, we install fonts in
another directory to avoid conflicts, then symlink non-conflicting fonts
to the fontconfig-controlled directory.
To be fair, I wrote the above statement. I'm confused about your
statement. What you're saying is correct with the exception that
there aren't really conflicts with Fontconfig. There are just fonts
we'd rather have it avoid since they render poorly. Regardless,
though, how would you suggest fixing the wording?
Fontconfig and extra fonts:
There seems to be 2 types of font packages; those fontconfig will use by
default, those it won't.
No, Fontconfig will use everything it finds. The "knows by default"
is that /etc/fonts.conf ships with a set of well known font packages
listed as aliases for monospace, sans and serif.
I'm assuming nothing needs to be done for the
former and it just works? As for the latter, do they all require
replacing an existing font family like the dejavu example shows?
In all cases, it just works if you specify the font you want to use.
The rub is that many applications which fetch fonts from fontconfig
(say, through pango), will request a generic family like monospace.
Then fontconfig will use the list in fonts.conf as the preferred set
of fonts it looks to first to try to render the characters.
In the case of dejavu, it is a drop in replacement for Bitstream Vera,
but with much better Unicode coverage. Unfortunately, it is not
listed in the preference matching in fonts.conf. Fontconfig is highly
configurable, but I never figured out how to put this very nice font
near the top of the preference list without hammering fonts.conf.
Without dejavu in the preference list, requesting a generic family
like sans would probably return the FreeFont fonts for many languages
since it has very good Unicode coverage. However, it's ugly.
So, to answer your question, nothing needs to be done to make
Fontconfig use new fonts. Drop it in a location FC is aware of, run
fc-cache and off you go. However, the above fix is a very nice tweak
to allow DejaVu to be my generic font.
The usernotes link is way down on the page.
I couldn't decide a better place. If you see a better spot, I'll move it.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
