From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Adrian Robert Newsgroups: gmane.emacs.devel Subject: Re: macos.texi updated Date: 25 Sep 2005 10:20:31 -0400 Message-ID: References: <8C0A68AE-EF12-4D6C-9879-D0FF3B04DE1B@mac.com> <87r7bhw2o8.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1127665792 25459 80.91.229.2 (25 Sep 2005 16:29:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 25 Sep 2005 16:29:52 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 25 18:29:51 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EJZMT-0007o8-Jj for ged-emacs-devel@m.gmane.org; Sun, 25 Sep 2005 18:28:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EJZMS-0002NJ-Ou for ged-emacs-devel@m.gmane.org; Sun, 25 Sep 2005 12:28:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EJZLL-00020l-N5 for emacs-devel@gnu.org; Sun, 25 Sep 2005 12:27:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EJZLK-0001zl-8j for emacs-devel@gnu.org; Sun, 25 Sep 2005 12:27:10 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EJZIo-0000bG-KD for emacs-devel@gnu.org; Sun, 25 Sep 2005 12:24:34 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1EJZ5B-0007eH-T2 for emacs-devel@gnu.org; Sun, 25 Sep 2005 12:10:30 -0400 Original-Received: from root by ciao.gmane.org with local (Exim 4.43) id 1EJZ4o-0004tj-1b for emacs-devel@gnu.org; Sun, 25 Sep 2005 18:10:06 +0200 Original-Received: from user-0cdfroq.cable.mindspring.com ([24.215.239.26]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 25 Sep 2005 18:10:06 +0200 Original-Received: from arobert by user-0cdfroq.cable.mindspring.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 25 Sep 2005 18:10:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 50 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: user-0cdfroq.cable.mindspring.com X-Newsreader: Gnus v5.7/20.7 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:43214 Archived-At: > > screen. I was also trying to maintain backwards compatibility of > old > XLFDs, which I'm starting to think was unwise. I've made two > attempts at > Regarding this, I think it would be good for people working on > Emacs.app, w32, and Xft to get together and try to figure out what to > do with the font-naming problem. It seems like the current use of > XLFD may benefit from an overhaul to adjust to the currently popular > font technologies. Even in X11, while XLFD is needed at the lowest level to interact with the windowing system, is it really necessary to expose the user to it? In the old days when emacs-X11 was first developed, X11 users were used to specifying fonts in ...-*-*-*-*-... fashion. Nowadays, most apps shield them from this. Thus, maybe it's reasonable to develop a new emacs font specification style that's simpler, and use this even in the face code until the lowest level where interaction w/the window system takes place? In most applications, users specify a font this way: string: family float: point size bool: bold bool: italic One question is how to deal with systems that allow more user control. For example, on OS X, some fonts have "semi-bold", "light", "condensed", and other versions. On X11, you can specify the DPI screen resolution the font is optimized for, and font pixel size instead of point size. The former situation could be handled using a fontspec like this: ("family-name" point-size (list-of-attributes)) Standard emacs faces would use just "bold" and "italic" as attributes, but users could use others specific to their systems, which the window system code would recognize. Unrecognized attributes are ignored or warned about. This approach might also handle X11 things like DPI resolution. For example, one attribute might be "75-dpi". Finally, a mechanism for ensuring some font family names are cross-platform would be needed. One approach here would be the time-honored "map standard postscript names to system-specific ones": each system would have a list of its equivalent families for "courier", "times", and so on. Another approach would be the web method of using generic names like 'sans', 'serif', and 'fixed' in all emacs standard faces.