unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: When and how to register various font backends
Date: Fri, 14 Jun 2019 15:19:14 +0300	[thread overview]
Message-ID: <83blz0xsu5.fsf@gnu.org> (raw)
In-Reply-To: <m2h88s1qc6.fsf@gmail.com> (message from Robert Pluim on Fri, 14 Jun 2019 11:14:17 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org,  YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Date: Fri, 14 Jun 2019 11:14:17 +0200
> 
> Currently under X11 the font backends end up as
> 
> (xft xfthb x)
> 
> Reordering that to put xfthb first is a matter of reordering the
> register_font_driver calls in Fx_create_frame

That's true, but we don't want to have 3 font backends in the list,
because then looking for a font that isn't available on the system
will take much longer (Emacs tries to find the font with each backend
in turn).  We want to have only 2 backends by default.

> Since xfthb is strictly better than xft, as far as I can tell, and we
> want people to actually use it, we should just prefer it for emacs-27,
> and remove the xft and x backends in emacs-28.

I'm not sure removing x (and gdi on Windows) is a good idea, even in
Emacs 28.  I understand (more accurately, was told very recently) that
HarfBuzz was designed to be able to work with any font, not just OTF,
but I'm not sure our integration of HarfBuzz allows that.  We should
actively test that with old fonts, like bitmapped fonts and BDF,
before we make the decision.  For example, I suspect the methods we
currently use for finding fonts suitable for HarfBuzz filter out
non-OTF fonts (at least on Windows, this is definitely so).

> default-frame-alist and similar will still be available for people
> who absolutely want to turn it off

The main issue at hand is how to allow users to specify the
non-preferred backends when they want that.  See Yamamoto-san's
message about that.



  reply	other threads:[~2019-06-14 12:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 19:40 When and how to register various font backends Eli Zaretskii
2019-06-14  9:14 ` Robert Pluim
2019-06-14 12:19   ` Eli Zaretskii [this message]
2019-06-14 13:16     ` Robert Pluim
2019-06-14 14:47       ` Eli Zaretskii
2019-06-15  9:50         ` Eli Zaretskii
2019-06-17  3:03           ` Michael Welsh Duggan
2019-06-17  9:41           ` Robert Pluim
2019-06-17 16:01             ` Eli Zaretskii
2019-06-18  1:29               ` YAMAMOTO Mitsuharu
2019-06-18 17:26                 ` Eli Zaretskii
2019-06-18 23:21                   ` YAMAMOTO Mitsuharu
2019-06-19 16:42                     ` Eli Zaretskii
2019-06-14 16:54     ` Andy Moreton
2019-06-14 10:52 ` YAMAMOTO Mitsuharu
2019-06-14 11:52   ` Robert Pluim
2019-06-14 12:26     ` Eli Zaretskii
2019-06-14 13:24       ` Robert Pluim

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=83blz0xsu5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@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).