From: Mike FABIAN <mfabian@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, 39799@debbugs.gnu.org
Subject: bug#39799: 28.0.50; Most emoji sequences don’t render correctly
Date: Sat, 29 Feb 2020 11:45:10 +0100 [thread overview]
Message-ID: <s9dh7z9y8nd.fsf@taka.site> (raw)
In-Reply-To: <83mu91enpa.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 Feb 2020 11:40:17 +0200")
Eli Zaretskii <eliz@gnu.org> さんはかきました:
>> From: Mike FABIAN <mfabian@redhat.com>
>> Cc: Robert Pluim <rpluim@gmail.com>, 39799@debbugs.gnu.org
>> Date: Sat, 29 Feb 2020 08:50:40 +0100
>>
>> >> and #xFE0F is always composable according to composite.c, so I donʼt
>> >> understand why composing only works with Noto Color Emoji. Or does the
>> >> font need specific support for it?
>> >
>> > Yes, the font needs to have glyph variations, see
>> > font-variation-glyphs and its underlying font-backend method
>> > get_variation_glyphs.
>>
>> http://unicode.org/reports/tr51/#Presentation_Style
>>
>> doesn’t seem to say that the fonts should have the variations.
>
> Please elaborate: which part thereof says that, and what are the
> implications regarding the fonts?
I think it is a bit vague. It does not say that this should be handled
by the fonts having glyphs for both styles, it does not seems to say
that it should be handled by switching fonts according to the variation
either. Currently no font which implements both the text and the emoji
representation seems to exist. So currently one can only make it work by
switching fonts depending on whether one wants to show text or emoji
representation. Pango does it that way.
I don’t know whether this is supposed to be the “right” way to it.
> The rendering of Emoji sequences is handled in Emacs via the font
> backend: Emacs submits the sequence to the backend, and the backend
> returns one or more glyphs that should be used to display the
> sequence. Emacs only submits a sequence of characters to the backend
> if the sequence matches one of the composition rules in
> composition-function-table. And the possible match for such
> composition rules is limited to character sequences that have the same
> 'face' text property, which in particular means the same font. In the
> case of variation selectors as part of the characters to be composed,
> Emacs additionally tests that the face's font has a glyph for the
> specified variation selector.
So this would work if a font had both black and white glyphs and colored
glyphs and used the variation selectors to select the desired glyph.
Maybe there should be a font like this, but currently no such font seems
to exist.
> If you are saying some of the above contradicts Unicode, please point
> out which part(s) and why.
I don’t think it contradicts Unicode. At least I am not sure, I think
the specification is not clear how this should be done.
But even if it doesn’t contradict Unicode, it means that it won't work
well with currently available fonts.
--
Mike FABIAN <mfabian@redhat.com>
睡眠不足はいい仕事の敵だ。
next prev parent reply other threads:[~2020-02-29 10:45 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s9dh7z9y8nd.fsf@taka.site \
--to=mfabian@redhat.com \
--cc=39799@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.