On Wed, May 03, 2006 at 03:29:22PM -0700, Dan Nicholson wrote:
>
> >"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?
I used conflict for brevity in place of:
"poorly rendered Type1 or non-scalabe bitmapped fonts"
The thing is, the symlinks do not *prevent* anything. The installation
of X fonts in a place other than /usr/share/fonts is the prevention. The
symlinks *add* to fontconfig. I hope I'm being more clear this time
around. You paragraph explcitely state that the symlinks *are* the
prevention.
> 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.
Perhaps that can be clarified in the book? What you wrote here makes
perfect sense. What I read in the book left me wondering what "knows by
default" meant. And the "example" used (dejavu) is a package that
doesn't fit either definition because the book says it is known by
default but still requires editing. Basically, I think it would help if
you just say (for each package) this font package needs X for Y
purposes and then give the example of how to do Y. Also, what if
multiple font packages that support being used when monospace is
requested are installed? How to do manage order of preference?
> >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.
Depends on what information is intended to be in that wiki. From the
name of the wiki page, I'd say that all topics covered on the book page
are fair game. If that is the case, I'd place the notest link at or near
the top of the book page. Currently it only holds font info, but it
could include something from the earlier paragraphs causing the link to
be after-the-fact.
--
Archaic
Want control, education, and security from your operating system?
Hardened Linux From Scratch
http://www.linuxfromscratch.org/hlfs
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
