2.030: Coffee emoji not displaying correctly

[mpolden]

On version 1.017:

On 2.030:

Screenshot was taken in iTerm2. Has the emoji been removed from the latest version? (2.030)

[krono]

I'd say it was added. The first picture shows the 'coffee' from the Apple Color Emoji font.

[frankrolf]

What you are seeing on top is fallback to Apple Color Emoji.
On the bottom (as @krono correctly suggests), is U+2615 HOT BEVERAGE as rendered in Source Code Pro.
See the specimen page for a list of Emoji (and Emoji-like) code points supported in Source Code Pro (♪ ♫ ♥ ​♣​ ♦​ ♠​ ☺​ ☻ ​❤​ ☕​ 💩 ​🤖​ 🔒):
http://adobe-fonts.github.io/source-code-pro/

[mpolden]

Thanks. Is there a way to build the fonts without the emoji code points?

[pauldhunt]

@martinp yes, download the Adobe Font Development Kit for OpenType (here on GitHub). Remove the lines for any glyphs you don’t want in the final font from the Glyph Order and Alias Database file. Rebuild the fonts using the command in the Read Me for this project. Troubleshoot any error messages that may pop up during the process. Good luck!

[mpolden]

@pauldhunt That did it, thanks!

In case anyone should need step by step instructions:

1. Download the Adobe Font Development Kit from http://www.adobe.com/devnet/opentype/afdko.html and unpack it somewhere (e.g. ~/Downloads)
2. Clone this repo and checkout the most recent tag: git checkout 2.030-ro/1.050-it
3. Remove glyphs from GlyphOrderAndAliasDB: gsed -i'' -e "s/uni2615\tcoffee/coffee\tcoffee/" GlyphOrderAndAliasD
4. Add AFDK to your PATH: export PATH=$PATH:$HOME/Downloads/FDK-25-MAC.b65322/Tools/osx
5. Follow the instructions from the readme: cd Roman/Regular && makeotf -r

[miguelsousa]

Removing the lines from the GlyphOrderAndAliasDB file will prevent you from being able to build the TrueType fonts, I believe. Instead, it's better to change the name in the first column.

Changing the line from this,
uni2615 coffee
to this,
coffee coffee
will preserve the font's glyph order and won't assign a Unicode value to the coffee glyph.

[mpolden]

@miguelsousa Ok, I've updated my previous comment. Thanks!