RobertWinslow

> We need _OpenmojiMonochrome_ more than anyone needs _OpenmojiBlack_.... But, correct me if I’m wrong, all shapes would need to be merged to a compound path and even before that,...

> even greater would be to have this part of the npm run generate-font build pipeline and to use your OpenMoji-MonoChrome.ttf as OpenMoji-Black.ttf Thanks for the feedback. I'll certainly look...

I believe after #422, the answer to this question is definitively "yes".

Here's a comparison of how these characters are being rendered in the current version of the fonts. (In Chrome for MacOS) From left to right: color png, glyf_colr_0 font, system...

> the issues has been resolved, correct? Yes, kind of. The color font is perfect, and #426 added black elements to the line-supplement layer, as shown in the PNG column....

Some additional links: This branch has the html comparison tables I generated, as well as the scripts I used to generate them: https://github.com/RobertWinslow/openmoji/tree/black-font-comparison-ff-ne I also generated tables for inspecting individual...

If anyone would like to take on this task, the following may prove helpful: Here is a list of Japanese characters that appear in emojis: ココ,サ,月,有,指,得,割,無,可,申,合,空,祝,秘,営,満 And for inspiration, here...