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#54562: 28.0.91; Emoji sequence not composed Date: Tue, 29 Mar 2022 14:44:47 +0300 Message-ID: <83sfr17zkg.fsf@gnu.org> References: <87bkxu8k7t.fsf.ref@yahoo.com> <87bkxu8k7t.fsf@yahoo.com> <83wngiba3j.fsf@gnu.org> <874k3m8grb.fsf@yahoo.com> <87pmmauwtp.fsf@gmail.com> <87y20y6ypi.fsf@yahoo.com> <83pmmab53s.fsf@gnu.org> <87sfr66sb7.fsf@yahoo.com> <87a6deunjj.fsf@gmail.com> <87k0ch5x8k.fsf@yahoo.com> <83h77lb6km.fsf@gnu.org> <871qyod5d5.fsf@gnus.org> <87zglc2q14.fsf@yahoo.com> <87y20vtor6.fsf@gmail.com> <87a6db2ajo.fsf@yahoo.com> <87mthatt5h.fsf@gmail.com> <838rsu9twq.fsf@gnu.org> <875ynytfce.fsf@gmail.com> <837d8e9q6x.fsf@gnu.org> <871qymt96j.fsf@gmail.com> <834k3i9i1y.fsf@gnu.org> <87o81prq93.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25179"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, larsi@gnus.org, 54562@debbugs.gnu.org To: Robert Pluim Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Mar 29 13:46:01 2022 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 1nZAIT-0006N0-Jj for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 29 Mar 2022 13:46:01 +0200 Original-Received: from localhost ([::1]:38436 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nZAIS-0003vS-0O for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 29 Mar 2022 07:46:00 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:59850) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nZAHY-0003sG-PY for bug-gnu-emacs@gnu.org; Tue, 29 Mar 2022 07:45:08 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37912) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nZAHX-0003vc-4d for bug-gnu-emacs@gnu.org; Tue, 29 Mar 2022 07:45:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nZAHX-0004vh-2y for bug-gnu-emacs@gnu.org; Tue, 29 Mar 2022 07:45:03 -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, 29 Mar 2022 11:45:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54562 X-GNU-PR-Package: emacs Original-Received: via spool by 54562-submit@debbugs.gnu.org id=B54562.164855429218909 (code B ref 54562); Tue, 29 Mar 2022 11:45:03 +0000 Original-Received: (at 54562) by debbugs.gnu.org; 29 Mar 2022 11:44:52 +0000 Original-Received: from localhost ([127.0.0.1]:60041 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nZAHM-0004uv-D4 for submit@debbugs.gnu.org; Tue, 29 Mar 2022 07:44:52 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:43702) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nZAHK-0004uj-G7 for 54562@debbugs.gnu.org; Tue, 29 Mar 2022 07:44:50 -0400 Original-Received: from [2001:470:142:3::e] (port=33782 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nZAHF-0003ri-43; Tue, 29 Mar 2022 07:44:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=uOGPtd+VAaSbchjTgCuMIgahHx2WYFmSNqAN4dzEcio=; b=Daf5vZ9K+eUrH0lt6D4E LCT6Vt+YZMJI8ih80/0cyKn9h/Nm803Lw4S3MBdTChTHV0Uwo0FLcgmFOOBWalgSeBh4zpm/+Y+JV mVYPvi+dkEV2llG1EAS1fLnvM2NUkRIqzmnULHX6IFp5bE8yOzAwiaP/HnCBooG+xQnIQUqYHI6ls 4fOy13fvw0Px4CkI77W60QZrwtmk4/YbbIo+66Z1ElY2Z0aWGF1piJ0i7CfBgEXCvYzXkjXegB6JL hmYMx/n82uF7D6OFua8pmNskz27t23x92bwSPlXzaR8T1qAxyk06cvFsrrfP5DdM0jpFQlMYaqKhW gpEsl74VEHAd7g==; Original-Received: from [87.69.77.57] (port=3350 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 1nZAHD-0001xo-JI; Tue, 29 Mar 2022 07:44:43 -0400 In-Reply-To: <87o81prq93.fsf@gmail.com> (message from Robert Pluim on Tue, 29 Mar 2022 12:45:44 +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" Xref: news.gmane.io gmane.emacs.bugs:229044 Archived-At: > From: Robert Pluim > Cc: luangruo@yahoo.com, larsi@gnus.org, 54562@debbugs.gnu.org > Date: Tue, 29 Mar 2022 12:45:44 +0200 > > Eli> I thought about any Mn character whose canonical-combining-class > Eli> property is 200 and above. The COMBINING ENCLOSING stuff > Eli> will need to be added to that, of course. And we could have that > Eli> option have multiple possible values, not just on/off... > > OK. Would Me be ok for you, or would you specifically want only the > codepoints from the "Combining Diacritical Marks for Symbols" block? Using Me is fine with me. > I guess you'd want options like: > > 'all => combining-class + enclosing > 'enclosing > 'combining-class > > (did we want to cover the 'number followed U+20E3 => emoji' case with > an option too?) That's a separate issue, IMO, and it can be handled via auto-composition-emoji-eligible-codepoints, I think? We could even tell users to do that by themselves. > > Eli> Btw, for sequences that include a base character and 2 or more > Eli> diacritics, selecting a font that supports the first diacritic (the > Eli> one which triggers the composition) might not be enough, since the > Eli> rest of the diacritics could be absent from that font. Instead, we'd > Eli> need something like "find the font for each one of them and then use > Eli> the one which supports the largest subset of them". > > font_range currently only has access to the first diacritic, so that > would be a bigger change. And that subset had better have the same > size as the number of unique diacritics, otherwise itʼs unlikely to > work. We could perhaps avoid the complexity by rewriting the composition rule for diacritics. Instead of "\\c.\\c^+" with 1-character look-back, we could have several rules: "\\c.\\c^\\c^\\c^\\c^" with 4-character look-back "\\c.\\c^\\c^\\c^+" with 3-character look-back "\\c.\\c^\\c^+" with 2-character look-back "\\c.\\c^+" with 1-character look-back (in that order). I didn't test this, but if it works, maybe it could solve the problem without any deep changes on the C level.