From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Inaccuracy in NEWS.28
Date: Tue, 01 Mar 2022 16:45:24 +0200 [thread overview]
Message-ID: <83bkyplojf.fsf@gnu.org> (raw)
In-Reply-To: <87zgm9iy30.fsf@gmail.com> (message from Robert Pluim on Tue, 01 Mar 2022 14:47:31 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Tue, 01 Mar 2022 14:47:31 +0100
>
> Po> ** The Cairo graphics library is now used by default if present.
> Po> -'--with-cairo' is now the default, if the appropriate development files
> Po> -are found by 'configure'. Note that building with Cairo means using
> Po> -Pango instead of libXFT for font support. Since Pango 1.44 has
> Po> -removed support for bitmapped fonts, this may require you to adjust
> Po> -your font settings.
> Po> +'--with-cairo' is now the default, if the appropriate development
> Po> +files are found by 'configure'. Building with Cairo is known to cause
> Po> +some problems with bitmap fonts. This may require you to adjust your
> Po> +font settings, or to build with Xft support instead.
>
> Po> Note also that 'FontBackend' settings in ".Xdefaults" or
> Po> ".Xresources", or 'font-backend' frame parameter settings in your init
>
> I think this is fine. Note we do call some Pango api's when using the
> GTK font chooser, but I suspect you could never choose a bitmapped
> font that way anyway.
OK, so let's install this on the emacs-28 branch.
Thanks.
next prev parent reply other threads:[~2022-03-01 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fso22ryu.fsf.ref@yahoo.com>
2022-03-01 4:54 ` Inaccuracy in NEWS.28 Po Lu
2022-03-01 12:26 ` Eli Zaretskii
2022-03-01 12:46 ` Po Lu
2022-03-01 13:14 ` Eli Zaretskii
2022-03-01 13:22 ` Po Lu
2022-03-01 13:47 ` Robert Pluim
2022-03-01 14:45 ` Eli Zaretskii [this message]
2022-03-02 0:56 ` Po Lu
2022-03-02 8:25 ` Robert Pluim
2022-03-02 8:32 ` Po Lu
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=83bkyplojf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).