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 17:47:07 +0300 [thread overview]
Message-ID: <835zp8xlzo.fsf@gnu.org> (raw)
In-Reply-To: <m24l4s1f3w.fsf@gmail.com> (message from Robert Pluim on Fri, 14 Jun 2019 15:16:51 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Fri, 14 Jun 2019 15:16:51 +0200
>
> >>>>> On Fri, 14 Jun 2019 15:19:14 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> >> (xft xfthb x)
> >>
> >> Reordering that to put xfthb first is a matter of reordering the
> >> register_font_driver calls in Fx_create_frame
>
> Eli> That's true, but we don't want to have 3 font backends in the list,
> Eli> because then looking for a font that isn't available on the system
> Eli> will take much longer (Emacs tries to find the font with each backend
> Eli> in turn). We want to have only 2 backends by default.
>
> That I think pleads for your solution, where xfthb is preferred to xft
> unless xft is specifically requested.
Both solutions provide this, the difference is in how you request
specific backend, and at which point in frame's life cycle you
can/should request that.
> Eli> I'm not sure removing x (and gdi on Windows) is a good idea, even in
> Eli> Emacs 28. I understand (more accurately, was told very recently) that
> Eli> HarfBuzz was designed to be able to work with any font, not just OTF,
> Eli> but I'm not sure our integration of HarfBuzz allows that. We should
> Eli> actively test that with old fonts, like bitmapped fonts and BDF,
> Eli> before we make the decision. For example, I suspect the methods we
> Eli> currently use for finding fonts suitable for HarfBuzz filter out
> Eli> non-OTF fonts (at least on Windows, this is definitely so).
>
> OK. So itʼs just xft (and uniscribe) weʼd be removing, eventually.
We can only remove those if we require HarfBuzz and don't support
builds without HarfBuzz.
> (add-to-list 'default-frame-alist '(font-backend xft x)) works already, no? And
> presumably continues to work with your solution.
No, it doesn't work with my solution, at least not reliably, because I
didn't intend it to work.
next prev parent reply other threads:[~2019-06-14 14:47 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
2019-06-14 13:16 ` Robert Pluim
2019-06-14 14:47 ` Eli Zaretskii [this message]
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=835zp8xlzo.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).