amio / emoji.json Goto Github PK

View Code? Open in Web Editor NEW

288.0 6.0 153.0 681 KB

Just an emoji.json

JavaScript 100.00%

emoji json

emoji.json's Introduction

emoji.json

Just an emoji.json.

Generated from emoji-test.txt with this script.

NOTE: There are no Emoji versions 6.0-10.0 as a decision was made in 2017 to align emoji version numbers with their respective Unicode versions starting with version 11.0.

Usage

install with npm

npm install emoji.json then:

var emoji = require('emoji.json')
console.log(emoji[2])
// {
//   codes: '1F604',
//   char: '😄',
//   name: 'grinning face with smiling eyes',
//   category: 'Smileys & Emotion'
// }

if you care about file size:

var emojiCompact = require('emoji.json/emoji-compact.json')
console.log(emojiCompact)
// ["😀","😁","😂","🤣" ...]

fetch from web

emoji.json's People

Contributors

Stargazers

Watchers

Forkers

npmcdn-to-unpkg-bot carson-katri olriko kagatep calebeby alner feng-jy hk-skit crmiguez vandijkstef seigneurj wanjarus optimatex surajsdm xing-fox koddsson little-buddy miraheka2305 akhileshcoder vinci7 drj-io sancou tomatosoupcan dincs yonikt songshunyao castrocrea zsaraf erik7911 perfectcube jamesallan93 win7killer connorpmullins gmenessy darksoul11 tasha-urbancic marvennsuson opassion ashwynh21 51moke maxximustech doraetao xdeadc0de buffermet balajicurago kolosovsky serreri-andrea ablyyogeshsanger tstonelee daadaadaah qades iamyashasvi peizhongli ishigo1987 gauravchauhan sunxiaomingatcn sibbsnb chen153 clayton8011 logleo mediumhust tjjay17 ifoxxiedev mathster0598 mcustiel moshikh leekafai tristargod w51fan ashish221306 wanjiaang badr21b mderzhanivska aselkg buqle mberger75 dionomusuko abh1lashc17ui coolcodemy nikdorbaz richienb lyar1225 xinyuanyiqiao arkobat whkendny zl630s shubambhasin matheuscamarques giuseppesalvo msohailmemon kulsoommalik pierrestcyr suyanyan nsgkkk embraceyang inoro openhouse xxmemebigboyxx heyman333 iysf

emoji.json's Issues

Keywords

Jump from 12.0.0 to 12.1.0 seems to have lost the keywords property in the JSON; is there a way to get that back, so that the emojis remain more searchable?

It's handy having the subcategory included in the 'full' JSON, but putting it in the category string means it's much more difficult to separate the emojis into separated categories on user-facing applications (who want the major categories, but likely not so much the subcategories). Could the subcategory be put into a separate subcategory property?

Missing release

v14 is tagged but not released: https://github.com/amio/emoji.json/releases

Include Unicode version

I realise this is not directly available on either data source (1, 2) this script is based on, but it would be handy to include in the JSON which version of Unicode introduced which emoji. This way, emojis that are too recent to be reliably reproduced cross-platform could be easily filtered out from end user applications, if desired.

I guess the script could do multiple passes of the different versions of emoji-test.txt (12.0, 11.0, 5.0, 4.0, etc), and compare contents of each to figure out the introduction version for each emoji.

Many can't be displayed properly.

{
"no": 133,
"codes": "1F90E",
"char": "🤎",
"name": "⊛ brown heart",
"keywords": "brown | heart",
"category": "Smileys & Emotion"
},

new names contain ⊛ symbol

While scrolling through the list i noticed that the new names in the emoji.json begin with the ⊛ symbol.

{
    "no": 67,
    "codes": "1F976",
    "char": "🥶",
    "name": "⊛ cold face",
    "keywords": "blue-faced | cold | freezing | frostbite | icicles"
  }

On the unicode.org website it states

Recently-added emoji are marked by a ⊛ in the name and outlined images

Those symbols should probably not be part of the actual name

"Component for use in RGI sequences. Isolated images should ..." in some "keywords" properties (and ⊛ is in some emoji names)

Hi, thanks for the great little dataset! Just a heads up that:

The "red hair" and many others contain some bad data in the "keywords" property: "Component for use in RGI sequences. Isolated images should ...". Looks like it should be easy to filter out since these notes seem to consistently come after a new line character. See another example of this in the "safety vest" entry: "Used in a ZWJ sequence for service dog"
"guide dog" and many others contain the "new emoji" symbol (⊛) in their name.

Cheers!

Translations

Is there a way to get the same list but with languages other than english?

Optionally filter out not fully qualified emoji

Could (perhaps a third flavour of) a JSON file be generated that has filtered out the component, unqualified and minimally-qualified entries, leaving only those marked fully-qualified?

In real-world use cases, typically only the fully-qualified emojis are useful to the end user, and their minimally-qualified and unqualified counterparts tend to be either duplicates or display incorrectly.

And typically of course component emojis would not be displayed to the end user as-is.