The “Noto Color Emoji” font is a far better emoji font than “Emoji One” or “Emoji Two”.
“Emoji One” and “Emoji Two” not only lack all the emoji added to Unicode 10.0.0, they also render many sequences incorrectly. “Emoji One” and “Emoji Two” are only up-to-date with Unicode 9.0.0 (Emoji 4.0). But they render even some sequences which were already in Emoji 4.0 incorrectly, for example:
http://www.unicode.org/Public/emoji/4.0/emoji-zwj-sequences.txt
already contained:
1F3CC 1F3FB 200D 2640 FE0F ; Emoji_ZWJ_Sequence ; woman golfing: light skin tone # 8.0 [1] (🏌🏻♀️)
So this sequence was already there in Unicode 9.0.0.
Unicode 10.0.0 added 56 emoji and 183 new sequences in Emoji 5.0, all of them don’t work with “Emoji One” and “Emoji Two”.
“Noto Color Emoji” is up-to-date with Unicode 10.0.0 (Emoji 5.0) and renders all sequences in Emoji 5.0 correctly.
Therefore, it is much better to install “Noto Color Emoji” by default.
The attached picture shows “Emoji Two” on the left and “Noto Color Emoji” on the right. One can see that many emoji sequences are rendered as several characters with “Emoji One”.
<img alt="emoji-f27-emoji-one-noto-color-emoji-comparison.png" src="/fedora-workstation/issue/raw/a1c86604e281be5d5aef4d3d4200ccf72aab6c4ec53f1c5291c188d8af1760d4-emoji-f27-emoji-one-noto-color-emoji-comparison.png" />
Metadata Update from @petersen: - Issue tagged with: meeting
This is the exact same questions that you asked during the F27 development cycle. We said that we would revisit in 2 cycles. This is one cycle. It's getting annoying.
This commit make gtk not render such 'broken' sequences in the emoji chooser:
https://git.gnome.org/browse/gtk+/commit/?id=675a4111e9f48b1f2290eafdc0d9598fbe48e199
It should find its way into the next gtk release.
We discussed this today but did not reach a consensus yet. Will discuss again at the next meeting (January 29). @mfabian, if you want to attend, it'll be 9:30 EST in #fedora-meeting-2.
Sorry, 9:00 EST. Not 9:30.
I’ll try to attend, but it might be diffcult because I will be in the bus from Brno to Prague at that time (returning from devconf.cz).
I believe something like 6/9 working group members will be at devconf.cz - so we're unlikely to meet on the 29th. (we might have an ad-hoc in-person meeting over the weekend.)
OK, February 12 will be the next IRC meeting, then.
This change is approved at today's WG meeting (+5,1,-0).
We discussed this at the meeting, and switching to noto was approved (+5,1,-0) - while people appreciated the value of distinct branding, there doesn't seem to any momentum on the upstream Emojitwo project that would get it where we need - and being functional for users is important.
Changes that are needed: * We need to change gnome-themes-standard to require the noto fonts instead of the emojione fonts - this will make sure that the right fonts get installed on upgrade * We need to make sure that the fontconfig configuration on fedora 28 prefers the noto fonts if both are installed. * It looks like comps currently installs both sets of emoji fonts - probably the emojione fonts should not be installed by default.
Metadata Update from @catanzaro: - Issue untagged with: meeting
Changes that are needed: * We need to change gnome-themes-standard to require the noto fonts instead of the emojione fonts - this will make sure that the right fonts get installed on upgrade
I opened https://src.fedoraproject.org/rpms/gnome-themes-standard/pull-request/1 for this.
We need to make sure that the fontconfig configuration on fedora 28 prefers the noto fonts if both are installed.
I believe this is already the case but let's check with @tagoh.
It looks like comps currently installs both sets of emoji fonts - probably the emojione fonts should not be installed by default.
I opened https://pagure.io/fedora-comps/pull-request/214
We need to make sure that the fontconfig configuration on fedora 28 prefers the noto fonts if both are installed. I believe this is already the case but let's check with @tagoh.
That's true. Noto Color Emoji is preferred than EmojiOne on f28.
The changes should all be in F28 now.
Metadata Update from @catanzaro: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.