From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Inaccuracy in NEWS.28
Date: Tue, 01 Mar 2022 14:26:41 +0200 [thread overview]
Message-ID: <83o82pluym.fsf@gnu.org> (raw)
In-Reply-To: <87fso22ryu.fsf@yahoo.com> (message from Po Lu on Tue, 01 Mar 2022 12:54:01 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Date: Tue, 01 Mar 2022 12:54:01 +0800
>
> NEWS.28 says:
>
> Note that building with Cairo means using Pango instead of libXFT for
> font support. Since Pango 1.44 has removed support for bitmapped
> fonts, this may require you to adjust your font settings.
>
> But we don't use Pango anywhere except to parse GTK input method
> information and the output of the GTK font dialog.
>
> Cairo text display is unrelated to Pango, and bitmapped fonts will work
> there as long as they are supported by FreeType. Bitmapped fonts will
> also continue to work with the X server-side font driver, which is
> available in Cairo builds.
>
> So would anyone mind me simply deleting that part of NEWS.28, since it
> is plain out wrong?
I'm not sure it's so plain wrong. This text came out of prolonged
discussions we had back in January 2020 on emacs-devel, and it started
with this report:
https://lists.gnu.org/archive/html/emacs-devel/2020-01/msg00583.html
Please read that discussion, and also the followups:
https://lists.gnu.org/archive/html/emacs-devel/2020-01/msg00620.html
https://lists.gnu.org/archive/html/emacs-devel/2020-01/msg00739.html
https://lists.gnu.org/archive/html/emacs-devel/2020-01/msg00870.html
Maybe the description we now have in NEWS.28 is inaccurate, but the
problems were real. So if you think mentioning Pango there is
incorrect (but please explain why, as I don't think I agree with your
reasoning: AFAIK Pango is the text layout engine used by Cairo), then
perhaps we should say something different there to convey the same
message. And the message is still valid, AFAIK.
next prev parent reply other threads:[~2022-03-01 12:26 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 [this message]
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
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=83o82pluym.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).