https://bugzilla.redhat.com/show_bug.cgi?id=1514274 --- Comment #4 from Peter Oliver <mavit@xxxxxxxxxxxx> --- (In reply to Neal Gompa from comment #3) > General question: Why is Noto part of Twemoji? My understanding is that > these are different fonts altogether? See https://github.com/googlei18n/noto-emoji/issues/9: “The noto-emoji project is two things at the same time: • an open-source toolchain for converting SVG assets to TrueType with colored emoji glyphs; • freely licensed SVG assets for the Noto Emoji glyphs. After a few minor changes, our toolchain could also consume other free assets and generate optimized fonts for Twitter Emoji and Emoji One.” The trouble is, this work to separate the two parts hasn’t yet been done. Meanwhile, the Twemoji and Emoji Two projects are web-focused, producing PNGs for use on web pages but not traditional TTF fonts. This is my attempt to use the Noto tooling to build Twemoji into a TTF. I’m open to discussion about the approach. An alternative might be to modify the existing google-noto-emoji-fonts package to distribute the tooling for use by other packages, but, to be honest, I’m not sure exactly which files would need to be included. See also this email I sent to the Fonts SIG (https://lists.fedoraproject.org/archives/list/fonts@xxxxxxxxxxxxxxxxxxxxxxx/thread/O6C2BFTPST4YWCOVKVLI6PBSDXQ5FF7C/), and a similar attempt for the Emoji Two font (https://pagure.io/emojitwo-fonts). > > # Work around UTF-8 > > export LANG=zh_CN.UTF-8 > > Please use "C.UTF-8". In Fedora, that is the generic locale that offers full UTF-8 support. I based the spec on that of google-noto-emoji-fonts, which does this too. It wasn’t clear to me exactly what UTF-8 issue it was supposed to be working around, so I left it in for now. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
