https://bugs.kde.org/show_bug.cgi?id=390937
--- Comment #2 from Adrien Beau <adrienb...@gmail.com> --- Thanks for your detailed answer. I did not know about Noto Emoji, it is interesting to know there is some choice in this area. However, looking at https://github.com/googlei18n/noto-emoji/issues/36 it appears you need very recent fontconfig and/or cairo to have it working out of the box. Indeed, I removed Twitter Color Emoji, restored the Neon fontconfig files, and put NotoColorEmoji.ttf in ~/.local/share/fonts as you suggested, and it was totally ignored by fontconfig. I also put NotoEmoji-Regular.ttf there, it was not ignored, but it only contains outdated black-and-white glyphs according to the noto-emoji README. The prepend hack may be ugly, but it also appears to be widely done by users in https://github.com/googlei18n/noto-emoji/issues/36 (at least until the very recent fontconfig version gets distributed more widely). Without it, I get glyphs from /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf and they suffer from a huge style clash: some of the most basic emojis are ugly black-and-white glyphs, while the rest has nice coloring. The emoji coverage is also very poor. Currently, it appears TwitterColorEmoji-SVGinOT.ttf is the one providing a font with full support and consistent style that just works under the Xenial software stack. The prepend hack, while unsavory, seems necessary to make it work in all cases. (Or maybe getting rid of DevaVuSans is a solution...) I also tried renaming 56-neon-noto.conf to 56-x-neon-noto.conf and it solves my issue as you expected. Thanks! Should I close this issue, or would you prefer to keep it open to include a workaround in your package? -- You are receiving this mail because: You are watching all bug changes.
