[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: TeX & XLFD
- To: email@example.com
- Subject: Re: TeX & XLFD
- From: firstname.lastname@example.org (Pierre MacKay)
- Date: Thu, 9 Sep 93 16:42:42 -0700
- Cc: email@example.com, firstname.lastname@example.org
- Flags: 000000000000
- In-Reply-To: Karl Berry's message of Mon, 6 Sep 1993 18:59:05 -0400 <199309062259.AA00406@ra.cs.umb.edu>
It is somewhat bizarre for TeX, which established its font namings
back in the very early 80s to be accused of reinventing things by
a relative newcomer like X.
In any case, as karl points out, texfonts.map can alias font
names of any reasonable sort. The problem does not lie there,
it continues to lie in the wretched limitations of the
You can't even use the basic
XLFD string (have I lost count?) in an 8+3 environment.
If you have a good aliasing mechanism, and a reasonable
filename space, it really doesn't matter very much.
Show an XLFD string to a traditional typesetting firm
(which may just have some knowledge about fonts) and
see where it gets you.
Email concerned with UnixTeX distribution software should be sent primarily
to: email@example.com Elizabeth Tachikawa
otherwise to: firstname.lastname@example.org Pierre A. MacKay
Smail: Northwest Computing Support Center Resident Druid for
Thomson Hall, Mail Stop DR-10 Unix-flavored TeX
University of Washington
Seattle, WA 98195