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 17:29:33 +0300 Message-ID: <83a7202gc3.fsf@gnu.org> References: <20200517165953.000044d2@web.de> <83lflqblp0.fsf@gnu.org> <83ftbybio3.fsf@gnu.org> <83zha69xs2.fsf@gnu.org> <83367x9qeq.fsf@gnu.org> <0ccae2a4-533b-d15c-2884-c2f00b067776@gmail.com> <83wo5987mk.fsf@gnu.org> <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> <83y2pk2nzy.fsf@gnu.org> <895400a0-a87a-70fe-b6ca-85c14c4745fa@gmail.com> 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="120487"; 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 16:30:28 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 1jc8gu-000VH2-Qi for ged-emacs-devel@m.gmane-mx.org; Fri, 22 May 2020 16:30:28 +0200 Original-Received: from localhost ([::1]:36474 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jc8gt-0004iL-PM for ged-emacs-devel@m.gmane-mx.org; Fri, 22 May 2020 10:30:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56394) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jc8fz-0003el-9E for emacs-devel@gnu.org; Fri, 22 May 2020 10:29:31 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49289) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jc8fx-00010d-VN; Fri, 22 May 2020 10:29:30 -0400 Original-Received: from [176.228.60.248] (port=1363 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jc8fv-0007lf-UI; Fri, 22 May 2020 10:29:28 -0400 In-Reply-To: <895400a0-a87a-70fe-b6ca-85c14c4745fa@gmail.com> (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Fri, 22 May 2020 09:26:05 -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:251229 Archived-At: > Cc: pipcet@gmail.com, alan@idiocy.org, emacs-devel@gnu.org > From: Clément Pit-Claudel > Date: Fri, 22 May 2020 09:26:05 -0400 > > > In general, I envision that people would use the font they find > > acceptable for the ligatures they want/need in each mode or buffer > > where they need that. If for some reason different fonts could > > determine which ligatures you do NOT want to see, then I guess we will > > have to provide some easy-to-use UI for that, which would manipulate > > the relevant data structures under the hood. Alternatively each font > > could require a separate composition function to go with it. > > It would be weird for Emacs to be the only program that requires re-encoding the entire ligature logic of each font it attempts to use. Different fonts offer different ligatures, and if I want to select a subset the font itself provides variants that let me do this. Meanwhile, I hope that we can make Emacs act like browsers or other editors in that if I select a font it will just, by default, use the ligatures that this font provides according to the logic embedded in the font. If this is a real problem, it should be possible to have a function that will extract all the ligatures supported by a font, I think. But I don't think I agree with the "logic embedded in the font" part. I think we should let the user control which ligatures are really used.