From: Eli Zaretskii <eliz@gnu.org>
To: mfabian@redhat.com, rpluim@gmail.com
Cc: 39799@debbugs.gnu.org
Subject: bug#39799: 28.0.50; Most emoji sequences don’t render correctly
Date: Fri, 28 Feb 2020 23:02:12 +0200 [thread overview]
Message-ID: <831rqefmsr.fsf@gnu.org> (raw)
In-Reply-To: <835zfqfohj.fsf@gnu.org> (message from Eli Zaretskii on Fri, 28 Feb 2020 22:25:44 +0200)
> Date: Fri, 28 Feb 2020 22:25:44 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 39799@debbugs.gnu.org
>
> Hmm... it's possible I was confused, and the functions I mentioned are
> unrelated to variation selectors. To see if that's so, try to
> configure composition-function-table to display such sequences as
> composed characters, and see what happens when you use a proper font
> (e.g., the one with which Gedit displays the variations).
Looking into this some more reveals that we already have
composition-function-table set up for variation selectors, see the end
of lisp/language/japanese.el. Not sure why it's in japanese.el, but
the code doesn't seem to be specific to Japanese characters, unless
I'm missing something. So some debugging is required to understand
why we don't display sequences with variation selectors as intended.
Maybe DejaVu Sans doesn't support that? What if you try
emacs -Q -fn Noto Color Emoji"
does Emacs built with HarfBuzz then display the variation sequences as
expected?
next prev parent reply other threads:[~2020-02-28 21:02 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 14:28 bug#39799: 28.0.50; Most emoji sequences don’t render correctly Mike FABIAN
2020-02-28 7:14 ` Eli Zaretskii
2020-02-28 7:36 ` Mike FABIAN
2020-02-28 8:25 ` Eli Zaretskii
2020-02-28 12:21 ` Robert Pluim
2020-02-28 12:46 ` Mike FABIAN
2020-02-28 13:19 ` Robert Pluim
2020-02-28 13:50 ` Mike FABIAN
2020-02-28 13:56 ` Eli Zaretskii
2020-02-28 14:44 ` Mike FABIAN
2020-02-28 13:08 ` Eli Zaretskii
2020-02-28 13:47 ` Mike FABIAN
2020-02-28 13:54 ` Eli Zaretskii
2020-02-28 14:14 ` Robert Pluim
2020-02-28 14:45 ` Eli Zaretskii
2020-02-28 15:32 ` Mike FABIAN
2020-02-28 15:57 ` Robert Pluim
2020-02-28 15:39 ` Robert Pluim
2020-02-28 16:38 ` Mike FABIAN
2020-02-28 14:46 ` Eli Zaretskii
2020-02-28 15:35 ` Robert Pluim
2020-02-28 15:44 ` Eli Zaretskii
2020-02-28 16:24 ` Robert Pluim
2020-02-28 17:30 ` Mike FABIAN
2020-02-28 17:55 ` Mike FABIAN
2020-02-28 18:01 ` Robert Pluim
2020-02-28 19:29 ` Mike FABIAN
2020-02-28 19:34 ` Mike FABIAN
2020-02-28 21:32 ` Mike FABIAN
2020-02-28 21:38 ` Robert Pluim
2020-02-28 20:21 ` Eli Zaretskii
2020-02-28 20:25 ` Eli Zaretskii
2020-02-28 21:02 ` Eli Zaretskii [this message]
2020-02-28 21:47 ` Robert Pluim
2020-02-28 22:07 ` Eli Zaretskii
2020-02-29 7:50 ` Mike FABIAN
2020-02-29 9:40 ` Eli Zaretskii
2020-02-29 10:45 ` Mike FABIAN
2020-02-28 21:10 ` Mike FABIAN
2020-02-28 21:49 ` Eli Zaretskii
2020-02-29 7:59 ` Mike FABIAN
2020-02-29 10:04 ` Eli Zaretskii
2020-02-29 11:14 ` Mike FABIAN
2020-02-29 11:52 ` Eli Zaretskii
2020-02-29 16:59 ` Mike FABIAN
2020-02-28 20:13 ` Eli Zaretskii
2020-02-28 20:38 ` Robert Pluim
2020-02-28 20:55 ` Eli Zaretskii
2020-02-28 21:22 ` Robert Pluim
2020-02-28 21:27 ` Mike FABIAN
2020-02-28 21:52 ` Eli Zaretskii
2020-02-29 8:01 ` Mike FABIAN
2020-02-29 9:49 ` Eli Zaretskii
2020-02-29 10:26 ` Mike FABIAN
2020-02-29 11:19 ` Eli Zaretskii
2020-02-29 11:36 ` Mike FABIAN
2020-02-29 11:58 ` Eli Zaretskii
2020-02-29 17:03 ` Mike FABIAN
2020-02-29 17:19 ` Eli Zaretskii
2020-02-29 11:41 ` Mike FABIAN
2020-02-29 12:02 ` Eli Zaretskii
2020-02-29 17:14 ` Mike FABIAN
2020-02-29 17:27 ` Eli Zaretskii
2020-03-02 9:10 ` Robert Pluim
2020-03-02 11:02 ` Eli Zaretskii
2020-02-28 21:14 ` Mike FABIAN
2020-02-28 21:50 ` Eli Zaretskii
2020-02-28 16:19 ` Eli Zaretskii
2020-02-28 16:39 ` Robert Pluim
2020-02-28 20:16 ` Eli Zaretskii
2020-02-28 20:56 ` Robert Pluim
2021-09-20 20:38 ` Robert Pluim
2021-09-21 9:16 ` Eli Zaretskii
2021-09-21 10:34 ` Robert Pluim
2021-09-21 10:54 ` Eli Zaretskii
2021-09-21 11:31 ` Eli Zaretskii
2021-09-21 17:43 ` Robert Pluim
2021-09-21 18:28 ` Eli Zaretskii
2021-09-22 9:02 ` Robert Pluim
2021-09-24 19:28 ` Mike FABIAN
2021-09-25 5:55 ` Eli Zaretskii
2021-09-25 7:35 ` Mike FABIAN
2021-09-25 9:19 ` Eli Zaretskii
2021-11-06 18:59 ` Lars Ingebrigtsen
2021-09-21 11:48 ` Mike FABIAN
2021-09-21 11:58 ` Eli Zaretskii
2021-09-21 12:27 ` Mike FABIAN
2021-09-21 12:37 ` Eli Zaretskii
2021-09-21 12:50 ` Robert Pluim
2021-09-21 13:06 ` Eli Zaretskii
2021-09-21 13:25 ` Mike FABIAN
2021-09-21 13:53 ` Robert Pluim
2021-09-21 14:19 ` Eli Zaretskii
2021-09-21 14:43 ` Robert Pluim
2021-09-21 15:58 ` Eli Zaretskii
2021-09-21 16:10 ` Robert Pluim
2021-09-21 16:23 ` Eli Zaretskii
2021-09-21 16:50 ` Eli Zaretskii
2021-09-21 18:20 ` Eli Zaretskii
2021-09-22 8:59 ` Robert Pluim
2021-09-22 13:47 ` Eli Zaretskii
2021-09-24 11:41 ` Robert Pluim
2021-09-24 12:04 ` Eli Zaretskii
2021-09-24 12:10 ` Robert Pluim
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=831rqefmsr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39799@debbugs.gnu.org \
--cc=mfabian@redhat.com \
--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).