From xemacs-m  Fri Jan  3 10:47:48 1997
Received: from apollo.jeeves.net (apollo.jeeves.net [206.242.44.75])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id KAA03045 for <xemacs-beta@xemacs.org>; Fri, 3 Jan 1997 10:46:43 -0600 (CST)
From: repayne@jeeves.net
Received: (from uucp@localhost) by apollo.jeeves.net (8.7.6/8.7.3) id KAA09702; Fri, 3 Jan 1997 10:45:34 -0600 (CST)
Message-Id: <199701031645.KAA09702@apollo.jeeves.net>
Received: from rosebank.jeeves.net(206.242.44.58) by apollo.jeeves.net via smap (V1.3)
	id sma009700; Fri Jan  3 10:45:31 1997
Sender: repayne@jeeves.net
Cc: xemacs-beta@xemacs.org
MIME-Version: 1.0
Date: Fri, 03 Jan 1997 10:46:25 -0600 (CST)
Subject: Fwd: Re: Suggestion and general remarks regarding faces.
X-Mailer: Jeeves by AetherWorks, version Dec  9 1996
X-Jeeves-State: 1
X-Priority: 3 (Normal)
Reply-To: repayne@jeeves.net
Content-Type: multipart/mixed; boundary="-=_=_4fc9ca8efffb860efffb8f8"
To: <elan@jeeves.net>

---=_=_4fc9ca8efffb860efffb8f8
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

This sounds like something that would be interesting, though probably
difficult, for Jeeves implementation.  Whaddya think?

-rob
---=_=_4fc9ca8efffb860efffb8f8
Content-Type: message/rfc822; name="Forwarded message"
Content-Description: Forwarded message
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="Forwarded message"

Return-Path: xemacs-beta-request@xemacs.org
Received: (from uucp@localhost) by apollo.jeeves.net (8.7.6/8.7.3) id IAA08175 for <repayne@jeeves.net>; Fri, 3 Jan 1997 08:46:24 -0600 (CST)
Received: from xemacs.cs.uiuc.edu(128.174.252.16) by apollo.jeeves.net via smap (V1.3)
	id sma008173; Fri Jan  3 08:46:14 1997
Received: (from xemacs-m@localhost)
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4)
	  id IAA02604; Fri, 3 Jan 1997 08:38:50 -0600 (CST)
Resent-Date: Fri, 3 Jan 1997 08:38:50 -0600 (CST)
Date: Fri, 3 Jan 1997 06:37:48 -0800
Message-Id: <199701031437.GAA20888@newman>
From: "William M. Perry" <wmperry@aventail.com>
To: Steven L Baur <steve@miranova.com>
Cc: xemacs-beta@xemacs.org
Subject: Re: Suggestion and general remarks regarding faces.
In-Reply-To: <m24th0hutz.fsf@altair.xemacs.org>
References: <x2ohf8qpfc.fsf@lemcbed.lem.uni-karlsruhe.de>
	<m24th0hutz.fsf@altair.xemacs.org>
Reply-to: wmperry@aventail.com
X-Face: O~Rn;(l][/-o1sALg4A@xpE:9-"'IR[%;,,!m7</SYF`{vYQ(&RI1&EiH[FvT;J}@f!4kfz
 x_!Y#=y{Uuj9GvUi=cPuajQ(Z42R[wE@{G,sn$qGr5g/wnb*"*ktI+,CD}1Z'wxrM2ag-r0p5I6\nA
 [WJopW_J.WY;
Resent-Message-ID: <"7gGxj1.0.de.udHpo"@xemacs>
Resent-From: xemacs-beta@xemacs.org
X-Mailing-List: <xemacs-beta@xemacs.org> archive/latest/824
X-Loop: xemacs-beta@xemacs.org
Precedence: list
Resent-Sender: xemacs-beta-request@xemacs.org

Steven L. Baur writes:
>>>>>> "Jens" == Jens Lautenbacher <jens@lemcbed.lem.uni-karlsruhe.de> writes:

>Jens> The new custom.el should be used to edit faces and save the
>Jens> edited values instead.
>
>The new custom is not compatible with the old, and would necessitate
>waiting for completion of Gnus 5.4 and the latest round of w3 changes.
>
>19.15 has got to be released ASAP.  My sanity requires it.  Two source
>code trees is driving me mad, and is getting in the way of doing more
>useful things than applying every patch twice, etc.
>
>We will be moving to the new custom in time, and I hope to see it
>(after the interface to it has been cleaned & prettied up) become the
>standard mechanism for customizing the whole editor.  I don't think
>now is the right time.

  One thing that I think should be in the next feature-ful XEmacs release
(as opposed to just bug-fixing) is a new font-model.  I've talked to chuck
and ben and RMS a little about this, and have a POC version worked up in
Elisp (font.el in the w3 distributions).

  What we need is something closer to the windows logical font model,
accessible at the lisp level.  With the current font package, you can
specify:

(setq my-font (make-font :size "24pt"
                         :family '("arial" "ookla" "sans-serif")))
-> [:family ("arial" "ookla" "sans-serif") :weight nil :style 0 :size "24pt" :registry nil :encoding nil]

The :family property allows you to specify an arbitrarily long list of font
families to use to satisfy a font request.  So if 24pt arial is not
available on your system, it will try to find 24pt ookla, and if that is
not available, then any 24pt sans-serif font will do.  Sizes can be
specified in points, pixels, inches, centimeters, picas, etc.

If anyone has time to try to implement this in C (you'd need to have a new
resolve_font device-methd), let me know and we can talk about it.  I don't
think I'll have time for a few months to actually implement it myself.

-Bill P.



---=_=_4fc9ca8efffb860efffb8f8--

