Expectations around variation selector handling about emoji-data HOT 3 CLOSED

The explanation is that it's like this for historical and backward compatibility reasons - originally iOS did not use the variation selector at all (it did not exist yet), so many codepoints rendered as emoji when no selector was present. As a result, iOS now uses FE0F for emoji-mode and FE0E for text mode, while other platforms use FE0F for emoji node and no selector for text mode. Because of this incompatibility, it's up to implementors to choose what happens when a bare maybe-emoji codepoint is presented.

from emoji-data.

Including the emoji properties in the output data is probably a good idea 👍

from emoji-data.

this has been fixed in PR #100 which will become release 4.0.0

i now use the fully-qualified version (including modifier) as the main codepoint sequence, with non-qualified versions appearing as an optional property. all images have been renamed to reflect this.

from emoji-data.