From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: new font-backend mechanism Date: Tue, 06 Jun 2006 13:16:43 +0900 Message-ID: References: <873bgdf6fo.fsf@pedrokroeger.net> <444385D4.3090802@swipnet.se> Reply-To: emacs-unicode@gnu.org NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1149567442 24903 80.91.229.2 (6 Jun 2006 04:17:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 6 Jun 2006 04:17:22 +0000 (UTC) Cc: Meik.Hellmund@math.uni-leipzig.de, jan.h.d@swipnet.se, sdl.web@gmail.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 06 06:17:20 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FnT0H-00066Y-Va for ged-emacs-devel@m.gmane.org; Tue, 06 Jun 2006 06:17:18 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FnT0H-0004h1-BB for ged-emacs-devel@m.gmane.org; Tue, 06 Jun 2006 00:17:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FnT04-0004fe-1N for emacs-devel@gnu.org; Tue, 06 Jun 2006 00:17:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FnT02-0004dM-CI for emacs-devel@gnu.org; Tue, 06 Jun 2006 00:17:03 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FnT02-0004dJ-77 for emacs-devel@gnu.org; Tue, 06 Jun 2006 00:17:02 -0400 Original-Received: from [150.29.246.133] (helo=mx1.aist.go.jp) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FnT7H-00033E-Mp; Tue, 06 Jun 2006 00:24:32 -0400 Original-Received: from smtp4.aist.go.jp ([150.29.246.12]) by mx1.aist.go.jp with ESMTP id k564Gs8w022320; Tue, 6 Jun 2006 13:16:54 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp4.aist.go.jp with ESMTP id k564Gnfr019162; Tue, 6 Jun 2006 13:16:49 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FnSzj-000888-00; Tue, 06 Jun 2006 13:16:43 +0900 Original-To: emacs-unicode@gnu.org In-reply-to: (message from Kenichi Handa on Mon, 17 Apr 2006 21:53:31 +0900) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) 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:55742 Archived-At: In article , Kenichi Handa writes: > Actually, after reading codes of XFT branch, I started to > design a new font handling mechanism. The basic plan is to > use multiple font-backends drivers (xcore, xft, windows, > bdf, atm, etc). The main motivation for this rewriting is > that the current XFT code in the branch is very difficult to > utilize fontconfig's help for font selection, and to drive > OTF fonts. And also, I want to clean up the current fairly > complicated font related codes (including many HAVE_XFT > conditionals, many XLFD parsing code, etc). > But, as there are many other works to be done, the progress > for the above code is slow. Please don't expect a quick > response on this matter. Anyway, here's the current font.h > file (not yet fully considered) with which you may get a > feeling of the design. I've just committed changes for this font-backend mechanism in emacs-unicode-2 branch. As I added two tags before and after the commit, you can see what are changed by: % cvs diff -Nu -r unicode-pre-font-backend -r unicode-post-font-backend The reason I dared not make a new branch is that the new codes don't affect the current behavior of emacs-unicode unless you configure with "--enable-font-backend" and run Emacs with the same arg. README.unicode contains some more information about the changes. We still need many more works to make using of font-backend the default. But, before going ahead, I'd like to ask people working on Windows and Mac porting to check if the current mechanism (APIs of font-driver) is sufficient for native fonts support. I think it is better to use emacs-unicode@gnu.org (not emacs-devel@gnu.org) for the further discussion on this matter to avoid disturbing the works for the official realease. So, people who are interested in it please join emacs-unicode mailing list. For that, as far as I remember, Eli can handle a request of subscribing. Eli, is it right? --- Kenichi Handa handa@m17n.org