From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 54562@debbugs.gnu.org
Subject: bug#54562: 28.0.91; Emoji sequence not composed
Date: Fri, 25 Mar 2022 13:27:44 +0300 [thread overview]
Message-ID: <83wngiba3j.fsf@gnu.org> (raw)
In-Reply-To: <87bkxu8k7t.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Date: Fri, 25 Mar 2022 17:17:26 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> The following Emoji does not display correctly:
>
> 7⃣️
>
> In other programs, it displays as the digit "7" inside a square, but
> inside Emacs it displays as the digit "7", followed by the blue square,
> and an empty hollow black square.
I think this means your default font doesn't support the U+20E3
COMBINING ENCLOSING KEYCAP character. Emacs cannot compose characters
that aren't supported by the font used for the base character. Here's
what I see in "C-u C-x =" on my system, when Emacs uses a font that
does support it (and where I do see "7" inside a square):
position: 148 of 150 (98%), column: 2
character: 7 (displayed as 7) (codepoint 55, #o67, #x37)
charset: ascii (ASCII (ISO646 IRV))
code point in charset: 0x37
script: latin
syntax: w which means: word
category: .:Base, a:ASCII, l:Latin, r:Roman
to input: type "C-x 8 RET 37" or "C-x 8 RET DIGIT SEVEN"
buffer code: #x37
file code: #x37 (encoded by coding system iso-latin-1-dos)
display: composed to form "7⃣️" (see below)
Composed with the following character(s) "⃣️" using this font:
harfbuzz:-outline-Symbola-normal-normal-normal-serif-16-*-*-*-p-*-iso8859-1
by these glyphs:
[0 2 55 26 8 0 7 11 0 nil]
[0 2 8419 2327 0 -10 4 10 4 nil]
[0 2 65039 3 4 0 1 0 1 [0 0 0]]
with these character(s):
⃣ (#x20e3) COMBINING ENCLOSING KEYCAP
️ (#xfe0f) VARIATION SELECTOR-16
next prev parent reply other threads:[~2022-03-25 10:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bkxu8k7t.fsf.ref@yahoo.com>
2022-03-25 9:17 ` bug#54562: 28.0.91; Emoji sequence not composed Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 10:27 ` Eli Zaretskii [this message]
2022-03-25 10:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 10:54 ` Robert Pluim
2022-03-25 11:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 12:15 ` Eli Zaretskii
2022-03-25 12:46 ` Andreas Schwab
2022-03-25 13:05 ` Eli Zaretskii
2022-03-25 13:14 ` Andreas Schwab
2022-03-25 13:30 ` Robert Pluim
2022-03-25 13:57 ` Andreas Schwab
2022-03-25 13:44 ` Eli Zaretskii
2022-03-25 14:03 ` Andreas Schwab
2022-03-25 14:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 14:14 ` Robert Pluim
2022-03-26 1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-26 5:56 ` Eli Zaretskii
2022-03-26 16:51 ` Lars Ingebrigtsen
2022-03-27 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-27 15:10 ` Robert Pluim
2022-03-28 0:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-28 7:47 ` Robert Pluim
2022-03-28 11:51 ` Eli Zaretskii
2022-03-28 12:46 ` Robert Pluim
2022-03-28 13:12 ` Eli Zaretskii
2022-03-28 14:59 ` Robert Pluim
2022-03-28 16:07 ` Eli Zaretskii
2022-03-29 10:45 ` Robert Pluim
2022-03-29 11:44 ` Eli Zaretskii
2022-03-29 14:50 ` Robert Pluim
2022-03-29 15:42 ` Eli Zaretskii
2022-03-29 15:59 ` Robert Pluim
2022-03-29 16:49 ` Eli Zaretskii
2022-03-28 13:19 ` Andreas Schwab
2022-03-28 15:01 ` Robert Pluim
2022-03-28 15:35 ` Andreas Schwab
2022-03-28 16:11 ` Eli Zaretskii
2022-03-28 16:20 ` Andreas Schwab
2022-03-28 16:26 ` Robert Pluim
2022-03-28 16:41 ` Andreas Schwab
2022-03-28 17:10 ` Eli Zaretskii
2022-03-28 17:14 ` Eli Zaretskii
2022-03-28 17:39 ` Andreas Schwab
2022-03-28 18:12 ` Eli Zaretskii
2022-03-28 18:14 ` Andreas Schwab
2022-03-28 18:15 ` Eli Zaretskii
2022-03-25 11:23 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wngiba3j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54562@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).