From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Ligature support Date: Fri, 05 Nov 2021 17:45:09 +0100 Message-ID: <87a6iiimay.fsf@gnus.org> References: <87cznths5j.fsf@gnus.org> <8ff3b131c53b9df49236@heytings.org> <834k91th5c.fsf@gnu.org> <8ff3b131c5fe09753ca0@heytings.org> <83mtmtru6l.fsf@gnu.org> <8ff3b131c57f741d04e5@heytings.org> <83lf2drqx6.fsf@gnu.org> <87lf2c3k0z.fsf@gnus.org> <83wnlwqocq.fsf@gnu.org> <87wnlwyox9.fsf@gnus.org> <83lf2cq7n5.fsf@gnu.org> <87wnlnkxbo.fsf@gnus.org> <83cznfdohr.fsf@gnu.org> <87zgqik9bk.fsf@gnus.org> <83v916d64z.fsf@gnu.org> <878ry2k6qz.fsf@gnus.org> <83tugqd488.fsf@gnu.org> <87zgqiiq8c.fsf@gnus.org> <83r1bud3or.fsf@gnu.org> <87r1buipf5.fsf@gnus.org> <83o86yd0ig.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7472"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 05 17:47:13 2021 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 1mj2My-0001el-Ia for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Nov 2021 17:47:12 +0100 Original-Received: from localhost ([::1]:42652 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mj2Mx-0006ZW-Gj for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Nov 2021 12:47:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38696) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mj2LB-0003fH-7n for emacs-devel@gnu.org; Fri, 05 Nov 2021 12:45:21 -0400 Original-Received: from quimby.gnus.org ([2a01:4f9:2b:f0f::2]:59544) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mj2L9-000588-3A; Fri, 05 Nov 2021 12:45:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2rKzMfSpKV+cQgARE1ZAxoL70zsvv3b+3Vi7GkSEhsU=; b=MRkYG4Ew62mgfuXUN6pL2KTD7D mbcXOXfvuA2pZ0kBofgWYxq07unE+7vyu0ph+JWo/4jVCu+QqtwMjCw1ShhyVegeSUdU59djgxTxU N0D3uoN6OWN9wNRuEFbOf1c2ZlLH3At0steXOgBpnFS2luIo35Y97HBQPtfaQRgqKAlc=; Original-Received: from [84.212.220.105] (helo=elva) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mj2L3-0006Rh-3M; Fri, 05 Nov 2021 17:45:16 +0100 X-Now-Playing: Coffins's _Defilements_: "Black Aspirin (Iron Monkey cover)" In-Reply-To: <83o86yd0ig.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 05 Nov 2021 18:34:47 +0200") Received-SPF: pass client-ip=2a01:4f9:2b:f0f::2; envelope-from=larsi@gnus.org; helo=quimby.gnus.org X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:278788 Archived-At: Eli Zaretskii writes: > For example, the mode line can show stuff like "=3D-", and the font > could have a ligature for that -- do we really want that ligature on > the mode line? That's a good point. On the other hand, perhaps we want to use a different font on the mode line when using one of these special fonts. > Or the font could have a ligature for "ffi" -- do we want a variable > named "efficient" be displayed with that ligature? I'd be surprised. Possibly, but probably not. But I don't think people will choose to use fonts for programming that have fonts like that. (Are there even any monospace fonts that have such ligatures?) But when rendering document using a variable-pitch font, then yes. >> But it's certainly possible -- having a switch to tweak which ligatures >> should be active on a per-mode/buffer basis is something we'd need to >> look at. I think we can look at that after we actually have ligatures >> displayed at all, though. =F0=9F=98=80 > > Displaying them is easy, just set up composition-function-table > accordingly (I can show you the code if you cannot figure that out). Yes, please -- I've been poking at that, but didn't find the right incantation. > That's the least of our problems. Well, it's one problem, and I think it's the one that has to be solved first. (I've now sent a message to the harfbuzz list to see whether they have any input in how to get harfbuff to cough up this list of strings based on the font.) For instance, see bug#51385 where they have a weirdo font that maps "[TRACE]" (and 260 other strings) to different glyphs. We need that list, because we certainly don't want to be passing "[TRACE]" to harfbuzz when not using that font. --=20 (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no