>>>> "kkm" == Kirill 'Big K' Katsnelson
<kkm(a)dtmx.com> writes:
kkm> Not only the division line between font and face properties
kkm> is random, it is different in Windows and in X. Faces should
kkm> be -- eh -- homogenized?
kkm> Is it possible to kick fonts away form the lisp level at all?
kkm> Fonts are not abstract enough, faces are.
No, it's not possible. There are four problems:
(1) The face properties may overspecify the font on any given system
(eg, color on a mono system, family on a TTY); in such a case the
face system will have to choose a compromise font. The user
should be able to override this arbitrary choice directly.
(2) The face properties may underspecify the font, in which case the
face system makes an arbitrary choice. Again, the user should be
able to override.
(3) Some font systems may provide properties the face system doesn't
know about. (This is really a special case of (2).) For example,
the X-TT family of X servers and font servers allows fonts with
arbitrary slants and weights to be created from a base font.
Should we deny users access to those features?
(4) Some characteristics that are important to users ("style") are
encoded as properties that may not map across character sets
("family": there may be -adobe-courier-*-iso-8859-5 for all I
know, but there is no -adobe-courier-*-jisx0208.1990-0) or may not
even be meaningful within a character set (most Unicode fonts have
a "family", but typically they are simply glommed together
versions of other fonts, and even from "good" vendors like
Microsoft you will occasionally find that Latin-1 and Latin-2
characters have quite different style).
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."