https://bugzilla.redhat.com/show_bug.cgi?id=1496761
Bastien Nocera <bnocera(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
CC| |fonts-bugs(a)lists.fedoraproj
| |ect.org,
| |i18n-bugs(a)lists.fedoraproje
| |ct.org, mclasen(a)redhat.com,
| |pnemade(a)redhat.com
Component|gnome-themes-standard |fontconfig
Fixed In Version| |fontconfig-2.12.6-3.fc27
| |fontconfig-2.12.6-3.fc26
Resolution|--- |ERRATA
Assignee|ignatenko(a)redhat.com |tagoh(a)redhat.com
Last Closed|2017-10-09 16:00:01 |2017-11-06 10:56:55
--- Comment #15 from Bastien Nocera <bnocera(a)redhat.com> ---
(In reply to Jeremy Bicha from comment #9)
(In reply to Bastien Nocera from comment #2)
> I sent an upstream patch to the list about this:
>
https://lists.freedesktop.org/archives/fontconfig/2017-October/thread.html
Really? Where?
https://cgit.freedesktop.org/fontconfig/commit/?id=c41c9220181b203d1cf1f6...
I hope you don't mind me reopening this for discussion for Fedora
28,
especially since as far as I can tell Fedora 27 doesn't include a color
emoji font by default.
That's a bug in gnome-themes-standard, not the bug we're discussing here about
fontconfig.
As I'm sure you're aware, newer version of the emojione font
are not
redistributable.
We already know, it's written as such in the package spec file:
http://pkgs.fedoraproject.org/cgit/rpms/eosrei-emojione-fonts.git/tree/eo...
I looked at emojitwo today and it looks like it requires
several grunt/node packages in order to build from source, but the emojitwo
build documentation is non-existent so I may be wrong.
So it's awkward for distros to package a dead font (emojione) and it's
difficult for them to package emojitwo.
We know all this, but decided that it was the best solution for this purpose
already. There should be discussions about this on the Fedora Workstation list,
as well as in the GNOME bugzilla and/or wiki. If in doubt about any of those,
I'd be happy repeating those arguments on the fontconfig list, if you send an
email there and CC: me.
Resetting the status of the bug, as the problem in question was already fixed
in an errata.
--
You are receiving this mail because:
You are on the CC list for the bug.