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.bugs Subject: bug#63731: [PATCH] Support Emoji Variation Sequence 16 (FE0F) where appropriate Date: Tue, 06 Jun 2023 14:53:41 +0300 Message-ID: <83sfb43iyi.fsf@gnu.org> References: <87a5xrzsph.fsf@stebalien.com> <875y88bhvr.fsf@gmail.com> <83ilc8eapd.fsf@gnu.org> <83edmvcpzl.fsf@gnu.org> <87wn0n9uol.fsf@gmail.com> <83a5xjcgev.fsf@gnu.org> <87sfbb9m4y.fsf@gmail.com> <87o7ly9t6b.fsf@gmail.com> <83edmuax13.fsf@gnu.org> <87fs7a9hl3.fsf@gmail.com> <834jnqaun6.fsf@gnu.org> <878rd29d9u.fsf@gmail.com> <83leh19kec.fsf@gnu.org> <877csijbuv.fsf@gmail.com> <83fs763vez.fsf@gnu.org> <87wn0ihvyj.fsf@gmail.com> <83cz2a3tsl.fsf@gnu.org> <87mt1ehtm7.fsf@gmail.com> <838rcx53cm.fsf@gnu.org> <87ilc1j41b.fsf@gmail.com> <837csh50dy.fsf@gnu.org> <875y81hwxn.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9081"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63731@debbugs.gnu.org, steven@stebalien.com To: Robert Pluim Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jun 06 13:54:21 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1q6VGX-00026J-5e for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 06 Jun 2023 13:54:21 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q6VGG-00088q-2k; Tue, 06 Jun 2023 07:54:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q6VGE-00088c-OG for bug-gnu-emacs@gnu.org; Tue, 06 Jun 2023 07:54:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1q6VGE-0004ZP-F4 for bug-gnu-emacs@gnu.org; Tue, 06 Jun 2023 07:54:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q6VGE-00022B-5I for bug-gnu-emacs@gnu.org; Tue, 06 Jun 2023 07:54:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 06 Jun 2023 11:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63731 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch fixed Original-Received: via spool by 63731-submit@debbugs.gnu.org id=B63731.16860524287795 (code B ref 63731); Tue, 06 Jun 2023 11:54:02 +0000 Original-Received: (at 63731) by debbugs.gnu.org; 6 Jun 2023 11:53:48 +0000 Original-Received: from localhost ([127.0.0.1]:51114 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q6VFz-00021f-V7 for submit@debbugs.gnu.org; Tue, 06 Jun 2023 07:53:48 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:57312) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q6VFy-00021S-9E for 63731@debbugs.gnu.org; Tue, 06 Jun 2023 07:53:46 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q6VFs-0004TY-PF; Tue, 06 Jun 2023 07:53:40 -0400 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=LXJk8XAAQFKj44VZNwwQYFEDNk2NXYwwCSmabvZtQxo=; b=NFPYSefdIgud cJ/rrNR5sXb+6SDxn8cCQLBM4cKzZBsNX0dyYAhcqr9kmmTnzKH9oweS3IVACZt/sxfMwQ4EVrReY PKAaesOjWZR4wQCfswQzhQurIO+ouhQepWOIXbI2reoxmgDJIuCwZUUKgYey9aWeMmcuiVlLOQi4W aKqztJoC4Gj3SSLBXk9NAAwEhX0OsBWaTlAxsQGFcouJ4Ssl8FP6LYj0nxw3kSGRAwZz50CSx7qPq RCXKSUFif24Hp0LpBn7Z8L/uaGAvw2+XBAZswlwuuQmSg2UoLDRvMXhtsE7LEVviuUdQ1zK8+c/Z2 gqK1W7BJGBxWVqAHgpe8oQ==; Original-Received: from [87.69.77.57] (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 1q6VFs-00077n-4i; Tue, 06 Jun 2023 07:53:40 -0400 In-Reply-To: <875y81hwxn.fsf@gmail.com> (message from Robert Pluim on Tue, 06 Jun 2023 09:28:04 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:263054 Archived-At: > From: Robert Pluim > Cc: 63731@debbugs.gnu.org, steven@stebalien.com > Date: Tue, 06 Jun 2023 09:28:04 +0200 > > >>>>> On Mon, 05 Jun 2023 19:39:37 +0300, Eli Zaretskii said: > > >> From: Robert Pluim > >> Cc: 63731@debbugs.gnu.org, steven@stebalien.com > >> Date: Mon, 05 Jun 2023 17:57:04 +0200 > >> > >> >>>>> On Mon, 05 Jun 2023 18:35:37 +0300, Eli Zaretskii said: > >> > Eli> Which forward rules would conflict with a backward rule triggered by > Eli> U+FE0E? > >> > >> All the ones for the non-emoji codepoints that still need to be > >> composed as emoji sometimes, eg U+261D: > >> > >> "\N{U+261D}" > >> "\N{U+261D}\N{U+1F3FB}" > >> "\N{U+261D}\N{U+1F3FC}" > >> "\N{U+261D}\N{U+1F3FD}" > >> "\N{U+261D}\N{U+1F3FE}" > >> "\N{U+261D}\N{U+1F3FF}" > > Eli> Couldn't we put these in the slots of #x1F3FB..#x1F3FF instead, as > Eli> backward rules? As long as we don't have a forward rule starting with > Eli> #x261D, we could have backward rules for it triggered by #x1F3Fx and > Eli> #xFE0x, right? > > Yes, we could invert the whole composition rules setup, and make them > all work backwards, but then it will almost certainly all break again > with the next release of Unicode. Adding a special case for FE0E in > font_range is going to be more robust. I don't think it could break, since such sequences are all likely to be triggered by special codepoints that follow the U+2xxx characters. Our win would be a much simpler setup. But okay, let's try to do it this way.