From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Inaccuracy in NEWS.28 Date: Tue, 01 Mar 2022 14:26:41 +0200 Message-ID: <83o82pluym.fsf@gnu.org> References: <87fso22ryu.fsf.ref@yahoo.com> <87fso22ryu.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3147"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 01 13:36:15 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP1ji-0000eJ-GU for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Mar 2022 13:36:14 +0100 Original-Received: from localhost ([::1]:58138 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nP1jf-0002Fw-Oy for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Mar 2022 07:36:11 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38498) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nP1ac-0005QT-NM for emacs-devel@gnu.org; Tue, 01 Mar 2022 07:26:50 -0500 Original-Received: from fencepost.gnu.org ([209.51.188.10]:37354) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nP1ab-00063o-2w; Tue, 01 Mar 2022 07:26:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=waowLVc/1QSJg7+EnAGibiiLVfJiymyrNmq6p+Z+BLk=; b=pXlTnBfjThuj BjORoNDYSC6tFAi/u5QdtevwC70bxqQyRA/+EA2ADudTGxU79IgdFHXB3zSj5DhmgIyli/aam/84U eZiMqh/ROgJZ8UqeLYnutP7A5gB5SalKtapPe+Wt2JgaeC+iyNpc59FA9BXRm/25PBJ7AWCp4bwzC haGDJdC/KsdS1nfLPChuzNC8EQUHlKwzuf+jTd2jmCYLBuI4ycw7RcHnLUXSKbkqkPdX5ALSoblEQ b0RmtLGVUD55WTQDINnZ/wKj0+yFiJ3X9tL/0G290roe7kNevuTUOUURaUmgNFzy2cD/jSUEsZ76p NeqEiprdG8FthNlCjzxT6Q==; Original-Received: from [87.69.77.57] (port=2494 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nP1aa-0007kY-4a; Tue, 01 Mar 2022 07:26:48 -0500 In-Reply-To: <87fso22ryu.fsf@yahoo.com> (message from Po Lu on Tue, 01 Mar 2022 12:54:01 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:286747 Archived-At: > From: Po Lu > 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.