https://bugs.kde.org/show_bug.cgi?id=390937
--- Comment #1 from Harald Sitter <sit...@kde.org> --- Well, if jriddell took the time to package Noto Emoji, you wouldn't need subpar third party packages at all... If I were you'd I'd just drop https://github.com/googlei18n/noto-emoji/tree/master/fonts into your ~/.fonts and delete the twemoji PPA package. That PPA config is fairly daftly written and I would not recommend using it. The reason it breaks your keepass is that it prepends its emoji font to everything containing the noto emoji font (which is just about everything as we've set up complete noto coverage in the 56-neon rule which is lexographically run before the twemoji config), so basically keepass will try to render every single character as an emoji, then as bitstream vera and then as noto (as per our rules). Mind you, it's funny how the emoji config picks such a high order value. If you were to configure user side fonts that'd happen in 50-* IIRC, so if the user configures a font rule that includes any of the popular color emoji fonts that'd also break font rendering because of how the emoji rule is written. So, really, the 56-twemoji-color.conf should be 49-x-twemoji-color.conf so it loads before any user customization. Or Maybe, and this is a big maybe, 50-c-twemoji-color.conf so it customizes on top of any user customization (which would still leave the problem of it basically breaking any font list including the mainstream color emoji fonts). All that said. What happens if you rename /etc/fonts/conf.d/56-neon-noto.conf to 56-x-neon-noto.conf? The way I see it if the noto config loads after the tw config all should be good. -- You are receiving this mail because: You are watching all bug changes.
