unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: Meik.Hellmund@math.uni-leipzig.de, jan.h.d@swipnet.se,
	sdl.web@gmail.com, emacs-devel@gnu.org
Subject: new font-backend mechanism
Date: Tue, 06 Jun 2006 13:16:43 +0900	[thread overview]
Message-ID: <E1FnSzj-000888-00@etlken> (raw)
In-Reply-To: <E1FVTER-000815-00@etlken> (message from Kenichi Handa on Mon, 17 Apr 2006 21:53:31 +0900)

In article <E1FVTER-000815-00@etlken>, Kenichi Handa <handa@m17n.org> 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 <eliz@gnu.org> can handle a request of subscribing.

Eli, is it right?

---
Kenichi Handa
handa@m17n.org

       reply	other threads:[~2006-06-06  4:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <873bgdf6fo.fsf@pedrokroeger.net>
     [not found] ` <444385D4.3090802@swipnet.se>
     [not found]   ` <E1FVTER-000815-00@etlken>
2006-06-06  4:16     ` Kenichi Handa [this message]
2006-06-06 19:00       ` new font-backend mechanism Eli Zaretskii
2006-06-08 15:11         ` Adrian Robert
2006-06-09  6:56           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1FnSzj-000888-00@etlken \
    --to=handa@m17n.org \
    --cc=Meik.Hellmund@math.uni-leipzig.de \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-unicode@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=sdl.web@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).