From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-27 7ec66a5: Document spacing issues with Xft for some fonts Date: Tue, 14 Jan 2020 18:00:26 +0200 Message-ID: <83d0bm58px.fsf@gnu.org> References: <20200114095124.30450.15618@vcs0.savannah.gnu.org> <20200114095126.2A901212AE@vcs0.savannah.gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="243234"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 14 17:01:52 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1irOdc-0010qF-0C for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Jan 2020 17:01:52 +0100 Original-Received: from localhost ([::1]:42724 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irOda-0003IK-9A for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Jan 2020 11:01:50 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48285) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irOc9-0002IH-QN for emacs-devel@gnu.org; Tue, 14 Jan 2020 11:00:22 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1irOc9-00022J-N6; Tue, 14 Jan 2020 11:00:21 -0500 Original-Received: from [176.228.60.248] (port=2280 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1irOc3-0001ly-GP; Tue, 14 Jan 2020 11:00:20 -0500 In-reply-to: (message from Robert Pluim on Tue, 14 Jan 2020 11:45:28 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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.org gmane.emacs.devel:244249 Archived-At: > From: Robert Pluim > Date: Tue, 14 Jan 2020 11:45:28 +0100 > > Eli, is it too soon for this? Hmm... soon? no, I don't think so. I just am not sure this is the best approach. First, I don't think we have enough data and experience to commit ourselves to remove Xft in Emacs 29, we should first see how painful such a removal will be wrt our users. Therefore, it might be better to turn Cairo ON by default on master, and only use Xft if Cairo is unavailable. If that proves to be a reliable configuration (i.e., we aren't flooded by complaints about the Cairo problems), then perhaps we will be able to remove Xft in Emacs 29 after all. WDYT? If you agree, then instead of mentioning the removal in Emacs 29, I'd prefer saying in NEWS that Xft is not actively maintained and has known problems with some modern fonts, and therefore we recommend against using it, as long as alternatives are available, Cairo being the best one of those.