From: Stefan Kangas <stefan@marxist.se>
To: Emacs developers <emacs-devel@gnu.org>, Robert Pluim <rpluim@gmail.com>
Subject: Re: master d8da850: Document cairo-related fallout to font-backend settings
Date: Mon, 20 Jan 2020 22:05:23 +0100 [thread overview]
Message-ID: <CADwFkm=9s1O8aKiGEE-KU=AV99zHBLJUAODVEtNax0MHDYoFoA@mail.gmail.com> (raw)
In-Reply-To: <20200120162050.08A5421148@vcs0.savannah.gnu.org>
Robert Pluim <rpluim@gmail.com> writes:
> +Note also that 'FontBackend' settings in .Xdefaults or .Xresources, or
> +'font-backend' frame parameter settings in your init files, may need
> +to be adjusted, as 'xft' is no longer a valid backend when using
> +Cairo. Use either 'ftcr' or 'ftcrhb' instead for FreeType and
> +FreeType + HarfBuzz respectively. 'x' is still a valid backend.
Should we say that FreeType + Harfbuzz is probably the correct choice
for most users, and perhaps also why? My concern is that people might
default to the shorter option and we could see unnecessary bug reports
about incorrect composition, etc.
Best regards,
Stefan Kangas
next parent reply other threads:[~2020-01-20 21:05 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 ` Stefan Kangas [this message]
2020-01-20 21:50 ` master d8da850: Document cairo-related fallout to font-backend settings Robert Pluim
2020-01-20 23:12 ` Stefan Kangas
2020-01-21 7:44 ` Robert Pluim
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='CADwFkm=9s1O8aKiGEE-KU=AV99zHBLJUAODVEtNax0MHDYoFoA@mail.gmail.com' \
--to=stefan@marxist.se \
--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).