unicode-emoji-json

• #18 https://emojipedia.org/emoji-15.1

There's no data content changes, only data structure change to data-by-group.json. See https://github.com/muan/unicode-emoji-json/pull/11 for details. Thanks to @DaveBagler. :)

This is not a major bump because we are not in 1.x land.

• #12 adds 15.0 emoji- https://emojipedia.org/emoji-15.0/
• #13 is fixed thanks to @nkalvi

#8.

See https://emojipedia.org/emoji-13.1/ and #7.

See https://emojipedia.org/emoji-13.0/.

[Breaking]

Rename object keys:

• fitzpatrick_scale -> skin_tone_support
• version -> unicode_version
• fitzpatrick_scale_version -> skin_tone_support_unicode_version

New object keys:

• emoji_version

What are the differences between emoji_version and unicode_version?

Good question. I was just reading up on this... For example, the first Unicode version to support emoji is v6.0, which is Emoji v1.0.

While a new Unicode version would introduce code points for emoji, for example,

• :onion: is Unicode 12.0/Emoji v12.0,

a new Emoji version would introduce emoji sequences utilizing existing code points.

• :person_with_red_hair: is Emoji v12.1 = :person: is Unicode v10.0/Emoji v5.0 + :red_hair:is Unicode 11.0/Emoji v11.0.

That is to say, even though Unicode v11.0 (June 2018) includes all the sequences required to make up :person_with_red_hair:, it was only officially introduced in Emoji v12.1 (Oct 2019).

You can read more to learn the differences on Emojipedia:

• Emoji Version 1.0
• Unicode Version 6.0

Emoji version is now exposed in the unicode data dump downloaded by the scripts, so I'm including them in the output.

Initial release with Emoji v12.0 data.

Fix emoji name parsing. Example changes:

• a_button_blood_type_ -> a_button
• flag_myanmar_burma_ -> flag_myanmar

6 name changes in total.

Bump emoji data to Emoji version v12.1. Which includes:

• New emoji (https://github.com/muan/unicode-emoji-json/compare/v0.0.3...v0.0.4)
• One name change man_with_chinese_cap -> man_with_skullcap