From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Jean-Christophe Helary <lists@traduction-libre.org>,
Robert Pluim <rpluim@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Better emoji support
Date: Sun, 19 Sep 2021 19:16:45 +0200 [thread overview]
Message-ID: <87bl4ozds2.fsf@gmail.com> (raw)
In-Reply-To: <87tuigmyez.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 19 Sep 2021 19:09:24 +0300")
Juri Linkov <juri@linkov.net> writes:
> Thanks, this is a nice change. I have a problem only with one character.
> Displaying NORTH EAST ARROW ↗ with emoji font is inappropriate to me.
>
> If adding this character to the emoji script was not a mistake,
> is it possible to customize this to display such characters
> as a symbol like before?
admin/unidata/emoji-data.txt contains a whole section where "omitted
code points have Emoji_Presentation=No", and AFAICT NORTH EAST ARROW
is one of those omitted code points.
IIUC, the Unicode standard means for those omitted characters to display
as "text" rather than as "emoji", unless they are followed by a
variation selector[1]; maybe some adjustments in fontset.el are in
order?
[1] http://www.unicode.org/reports/tr51/#Emoji_Presentation
next prev parent reply other threads:[~2021-09-19 17:16 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 9:19 Better emoji support Eli Zaretskii
2021-07-10 9:24 ` Robert Pluim
2021-07-10 9:37 ` Eli Zaretskii
2021-07-10 9:45 ` Robert Pluim
2021-07-10 9:48 ` Eli Zaretskii
2021-07-12 8:27 ` Robert Pluim
2021-07-12 14:02 ` Robert Pluim
2021-07-12 15:38 ` Robert Pluim
2021-07-12 15:59 ` Eli Zaretskii
2021-07-13 7:00 ` Jean Louis
2021-07-13 7:50 ` Robert Pluim
2021-07-15 15:15 ` Robert Pluim
2021-07-15 15:44 ` Eli Zaretskii
2021-09-13 12:36 ` Eli Zaretskii
2021-09-13 15:44 ` Robert Pluim
2021-09-13 16:07 ` Eli Zaretskii
2021-09-13 16:36 ` Jean-Christophe Helary
2021-09-17 13:01 ` Robert Pluim
2021-09-17 13:42 ` Jean-Christophe Helary
2021-09-17 13:50 ` Robert Pluim
2021-09-17 15:51 ` Kévin Le Gouguec
2021-09-17 16:43 ` Robert Pluim
2021-09-17 19:34 ` Kévin Le Gouguec
2021-09-19 18:27 ` Robert Pluim
2021-09-19 19:43 ` Kévin Le Gouguec
2021-09-20 4:23 ` Eli Zaretskii
2021-09-20 6:20 ` Kévin Le Gouguec
2021-09-20 6:53 ` Eli Zaretskii
2021-09-20 8:40 ` Robert Pluim
2021-09-20 9:53 ` Eli Zaretskii
2021-09-20 13:03 ` Robert Pluim
2021-09-20 13:15 ` Eli Zaretskii
2021-09-20 13:25 ` Eli Zaretskii
2021-09-20 13:50 ` Robert Pluim
2021-09-20 15:27 ` Eli Zaretskii
2021-09-20 17:32 ` Robert Pluim
2021-09-20 18:54 ` Eli Zaretskii
2021-09-20 19:30 ` Robert Pluim
2021-09-20 19:42 ` Eli Zaretskii
2021-09-20 20:05 ` Robert Pluim
2021-09-20 13:40 ` Robert Pluim
2021-09-20 13:45 ` Eli Zaretskii
2021-09-17 15:58 ` Jean-Christophe Helary
2021-09-17 16:35 ` Daniel Martín
2021-09-17 16:52 ` Robert Pluim
2021-09-17 15:39 ` Stephen Berman
2021-09-17 16:01 ` Eli Zaretskii
2021-09-17 16:34 ` Stephen Berman
2021-09-17 16:58 ` Robert Pluim
2021-09-17 17:05 ` Stephen Berman
2021-09-17 17:10 ` Robert Pluim
2021-09-17 17:17 ` Stephen Berman
2021-09-17 17:37 ` Better emoji support, " Robert Pluim
2021-09-17 17:49 ` Stephen Berman
2021-09-17 17:51 ` Robert Pluim
2021-09-17 18:53 ` martin rudalics
2021-09-17 18:58 ` Robert Pluim
2021-09-17 19:44 ` Stephen Berman
2021-09-17 18:53 ` martin rudalics
2021-09-17 16:55 ` martin rudalics
2021-09-17 18:48 ` Eli Zaretskii
2021-09-17 18:59 ` Robert Pluim
2021-09-18 5:39 ` Eli Zaretskii
2021-09-18 6:25 ` Eli Zaretskii
2021-09-19 16:09 ` Juri Linkov
2021-09-19 17:16 ` Kévin Le Gouguec [this message]
2021-09-19 18:20 ` Robert Pluim
2021-09-19 19:13 ` Robert Pluim
2021-09-19 17:24 ` Eli Zaretskii
2021-09-19 18:10 ` Robert Pluim
2021-09-19 18:29 ` Eli Zaretskii
2021-09-19 18:40 ` Robert Pluim
2021-09-19 18:34 ` 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=87bl4ozds2.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=lists@traduction-libre.org \
--cc=rpluim@gmail.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).