"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>> "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.
Neither of these should ever happen with proper property merging. The
default font would ALWAYS be fully specified. Either by the user or by a
combination of the user and window-system-specific defaults.
(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?
Nope. You should always be able to specify a font fully.
-bp