Package Details: ttf-twemoji-color 12.0.1-1

Git Clone URL: (read-only)
Package Base: ttf-twemoji-color
Description: A color and B&W emoji SVG-in-OpenType font with support for ZWJ, skin tone modifiers and country flags.
Upstream URL:
Keywords: color emoji font otf svg-in-ot ttf twemoji twemoji-color-font
Licenses: MIT, custom:CCPL:by-4.0
Conflicts: twemoji-color-font
Provides: twemoji-color-font
Replaces: twemoji-color-font
Submitter: Edgemaster
Maintainer: Edgemaster (eosrei)
Last Packager: Edgemaster
Votes: 79
Popularity: 0.446556
First Submitted: 2017-05-03 15:16
Last Updated: 2019-04-16 20:10

Pinned Comments

Edgemaster commented on 2017-06-08 14:31

v12.0.1 of the font is now available, supporting Unicode and Emoji 12 standards.

A manual installation step is required to configure your default system font and install the configuration file.

Note: Usage with fonts that already include emoji codepoints may give inconsistent/broken results, Bitstream Vera Sans is the chosen as the default as it includes no emoji by default. For further details, please see the project's README file for a discussion of the issues.

Latest Comments

1 2 3 4 5 6 Next › Last »

helvetica commented on 2019-05-01 23:00

Per upstream GitHub this project is dead thanks to licensing changes on the use of SVGs:

You'll want to switch to ttf-emojione as it is using the TTF provided by JoyPixels.

griffin commented on 2019-03-03 00:15

I'm not sure how much it makes sense to leave the two, especially when the other is orphaned, despite the differences in embedding styles. Do you think it makes sense to merge that one into this one despite that, or to leave the two? Having both is a bit confusing to users.

Edit: Hm, I see. On Discord for example, this package creates outlines for usernames with emojis on them but the other package gives them the full emoji. Strange.

Edgemaster commented on 2019-03-02 22:12

This package distributes the font with colour SVG glyphs in the OpenType font file. I'm unsure of how the ttf-twemoji embeds the glyphs in the font (possibly as bitmaps or PNG, depending on intended application support, or monochrome outlines). I was unaware of this other package until now.

Edit: Yes, it appears that the fedora upstream of ttf-twemoji embeds the glyphs as PNG inside of OpenType: The different embedding styles have different application support, at the last time I checked, but the situation may have improved in the intervening 2 years.

griffin commented on 2019-03-02 20:26

Can I ask what the differences between this package and are beside the source? The latter has been orphaned, and before adopting it, I wanted to know why we couldn't just merge the two/

CounterPillow commented on 2018-11-07 20:22

Installing this font makes it forcibly override all subtitle fonts in mpv, resulting in broken typesetting, so beware.

j1simon commented on 2018-03-01 14:46

@r3b311i0n I follow your advice and it works great! I see all emojis right on Firefox. This package should be done that automatically.

r3b311i0n commented on 2017-11-27 21:07

@Neros I'm not using this font ATM, but it looks like another font includes the Star and Crescent glyph and Firefox is using that font (DejaVu Sans, Symbola, etc.) to display it instead of Twemoji.

You should install Bitstream Vera, symlink 56-ttf-twemoji-color.conf from /etc/fonts/conf.avail to /etc/fonts/conf.d, and rebuild fontconfig cache (fc-cache -fv), and see if it works.
You could also try blacklisting the offending font using a fontconfig conf:

Neros commented on 2017-10-20 03:54

Is there an issue with Star and Crescent in Firefox for you?

It appears white for me, I don't know why and it's the only one.

WhyNotHugo commented on 2017-10-16 05:14

Yup, that's pretty much it. Upstream's font.conf broke almost every configuration out there, and since they're unwilling to fix it, the AUR package has its own.

Edgemaster commented on 2017-10-13 19:15

@joehillen This is a long-running saga both with upstream and the Arch packaging of it. (I was the original maintainer of a version of the package predating this one that bundled the upstream fontconfig).

Basically: the upstream fontconfig assumes that the system default font is Bitstream Vera and sets it as the first selection for the default font families. This is because Bitstream Vera is a font that does not contain any codepoints in the emoji ranges already which allows for a clean fallback to EmojiOneColor for all emoji characters. Other fonts often include incomplete sets of the emoji characters which gives inconsistent rendering results.

The version of the fontconfig with bundled with this package adds EmojiOneColor to the fallback lists for the default sans font family, and the Canatrell font as used by default by Gnome. It also binds EmojiOne to the emoji font family.

Bundling the upstream fontconfig resulted in lots of complaints that it broke all the system fonts, or defaulted the system to Bitstream against users' wishes.

Getting a single fontconfig to work with the multitude of end-user configurations and to avoid all glyph selection bugs appears to be impossible, this is an unfortunate limitation of what's possible with fontconfig congifurations. The upstream author has battled with this for quite a while, without being able to find a solution that works for everyone ☹️ (see the GitHub issue tracker).