From: Robert Pluim <rpluim@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: master d8da850: Document cairo-related fallout to font-backend settings
Date: Tue, 21 Jan 2020 08:44:39 +0100 [thread overview]
Message-ID: <m2r1ztqmmw.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkm=+YFLSVy71_b9scEU1C4eeh-ECfuKuhqqRjqgb6jwdtQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 21 Jan 2020 00:12:22 +0100")
>>>>> On Tue, 21 Jan 2020 00:12:22 +0100, Stefan Kangas <stefan@marxist.se> said:
Stefan> Thank you, that is much better. Please install.
Done.
>> [1] My master plan to remove as many different variations as possible
>> seems to get shot down every time I suggest it :-)
Stefan> BTW, if 'ftcr' only works when built without HarfBuzz, and 'ftcrhb'
Stefan> only works with HarfBuzz, can't we just use 'ftcr' and detect HarfBuzz
Stefan> automatically for the user?
I see two options:
1. give the Qftcrhb symbol the same name as Qftcr, which might do the
right thing, but would make it harder to work out whether HarfBuzz is
actually being used.
2. just say "If youʼre going to be modern, be modern: Cairo requires
HarfBuzz" (note that this is the path that Pango is taking).
Robert
next prev parent reply other threads:[~2020-01-21 7:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200120162048.23970.80216@vcs0.savannah.gnu.org>
[not found] ` <20200120162050.08A5421148@vcs0.savannah.gnu.org>
2020-01-20 21:05 ` master d8da850: Document cairo-related fallout to font-backend settings Stefan Kangas
2020-01-20 21:50 ` Robert Pluim
2020-01-20 23:12 ` Stefan Kangas
2020-01-21 7:44 ` Robert Pluim [this message]
2020-01-21 15:32 ` Eli Zaretskii
2020-01-21 15:39 ` Robert Pluim
2020-01-21 15:47 ` Eli Zaretskii
2020-01-22 7:22 ` Robert Pluim
2020-01-22 15:52 ` Eli Zaretskii
2020-01-22 16:11 ` Robert Pluim
2020-01-22 16:55 ` Eli Zaretskii
2020-01-22 16:53 ` Eli Zaretskii
2020-01-22 16:59 ` Robert Pluim
2020-01-22 17:38 ` Eli Zaretskii
2020-01-21 14:54 ` T.V Raman
2020-01-21 15:38 ` Robert Pluim
2020-01-21 16:54 ` Robert Pluim
2020-01-21 17:04 ` 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=m2r1ztqmmw.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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).