From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Ligatures (was: Unify the Platforms: Cairo+FreeType+Harfbuzz Everywhere (except TTY)) Date: Fri, 22 May 2020 22:44:46 +0300 Message-ID: <83wo5321qp.fsf@gnu.org> References: <20200517165953.000044d2@web.de> <99d4beed-88ae-b5cd-3ecb-a44325c8a1dc@gmail.com> <20200518215908.GA57594@breton.holly.idiocy.org> <83mu6481v3.fsf@gnu.org> <75a90563-51b4-d3b8-4832-fc0e2542af0d@gmail.com> <83blmi7hys.fsf@gnu.org> <837dx55qff.fsf@gnu.org> <834ks95cmz.fsf@gnu.org> <4faa291f-f2df-36d1-73d5-332b93a9b6d8@gmail.com> <83wo544hx5.fsf@gnu.org> <831rnc43ih.fsf@gnu.org> <83ftbs2jr5.fsf@gnu.org> <838shk2ga3.fsf@gnu.org> <835zcn3iao.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="79831"; mail-complaints-to="usenet@ciao.gmane.io" Cc: alan@idiocy.org, pipcet@gmail.com, emacs-devel@gnu.org To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 22 21:46:11 2020 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 1jcDcQ-000Kf3-DI for ged-emacs-devel@m.gmane-mx.org; Fri, 22 May 2020 21:46:10 +0200 Original-Received: from localhost ([::1]:51726 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jcDcP-0002bN-Ek for ged-emacs-devel@m.gmane-mx.org; Fri, 22 May 2020 15:46:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33540) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jcDb2-0008W8-VF for emacs-devel@gnu.org; Fri, 22 May 2020 15:44:44 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55327) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jcDb1-0003qQ-20; Fri, 22 May 2020 15:44:43 -0400 Original-Received: from [176.228.60.248] (port=4871 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jcDb0-000577-3R; Fri, 22 May 2020 15:44:42 -0400 In-Reply-To: (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Fri, 22 May 2020 15:33:59 -0400) 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.io gmane.emacs.devel:251246 Archived-At: > Cc: pipcet@gmail.com, alan@idiocy.org, emacs-devel@gnu.org > From: Clément Pit-Claudel > Date: Fri, 22 May 2020 15:33:59 -0400 > > >> But then how do you handle symbol ligatures? > > > > By using suitable regular expressions. E.g., you could take the list > > of ligatures in that FiraCode site and convert them into a regexp or a > > set of regexps. > > Thanks. I don't understand why we need to do this I'm not sure I follow. Do you understand why https://github.com/tonsky/FiraCode/wiki/Emacs-instructions includes a long list of strings to be replaced with ligatures? If so, why don't you understand the reason we need to specify similar things when we use automatic compositions? And who is "we" in this case? Users of these features indeed shouldn't need to mess with these long lists of character sequences, but why is it a problem if "we" the Emacs developers provide data bases of such sequences in advance, which user-facing features could use, hiding them behind much easier UI? > it seems surprising that we'll need extra Emacs-specific work for each and every font that includes ligatures). I don't understand how you got to this conclusion. This is true for prettify-symbols-mode, but that's exactly why I don't like that implementation, and why I think automatic compositions are a better way to go. And for automatic compositions we didn't yet decide that any user-level action is needed when you switch to another font, we are still discussing what is involved. Up front, I don't yet see why such font-specific adjustment would be required from users.