CodeFreezr / emojo

mojo for emoji
2 stars 0 forks source link

JSON fields #1

Open Crissov opened 6 years ago

Crissov commented 6 years ago
"No": 1, 
"Emoji": "πŸ˜€", 
"Category": "Smiley & Peoples", 
"SubCategpry": "face-positive", 
"Unicode": "U+1F600", 
"Name": "grinning face", 
"Tags": "face | grin | grinning face", 
"Shortcode": ":grinning:"

There is an obvious typo in SubCategory.

Some fields should be arrays, Tags, perhaps Categories, or name-value maps/objects, Shortcodes, Names (Unicode character vs. localized CLDR names). CLDR also offers localized keywords.

Unicode should be a number or array of numbers if you wanted to cover sequences. JSON unfortunately does not support hexadecimal notation.

Default presentation (text or emoji), existence of variation sequences (VS-15/16, U+FE0E/F), boolean status as skin tone modifier base and prefix or suffix in gender sequences could be useful; year or version of Unicode addition as well.

Crissov commented 6 years ago

Some sources for shortnames:

CodeFreezr commented 6 years ago

Upsalat. What kind of subtypo 😎. fixed.

Subarrays for tags could be a nice Idea. Even I tend to keep things as simple as possible, but not simpler.

The trouble is the unicode guys doesn't support anykind of "shortname", "shortcode" or "alpha_code". So there is no "final" decision authority what to use. At the moment I have synced with the eac.json. But will do a look up with all the other sources. Do you have an idea what Facebook / Messenger / Apple use as shortcodes? At the first glance emojipedia follows mostlikely the eac.json shortcodes.

I8N Names & Tags from CLDR is allready on my todo-list top10. This will blow up the json a lot, so I think about two jsons. One minimal, one CLDR. Or perhaps one json per language? 🎲 Another challenge CLDR is a bit behind v5. Only a subset of emoji v5 codepoints are supported.

And yes, Unicode should become an additional representation.

I would stuff like "Default Presentation", "Variation Sequences", "Modifier", "Year", "Unicode-Version" etc. put into the backlog. Perhaps for a "verbose" one.

Crissov commented 6 years ago

Apple does not use fixed short codes. They have emojis in their auto correct/complete suggestions.

Facebook supports replacing some ASCII emoticons and a limited set of β€œemotes” that can be extracted from their JS files. I don’t think there is other official, complete, up to date documentation of them.

emote2emojis: { 
slightsmile: '1f642', 
smile: '1f60a', 
frown: '1f61e', 
winktongue: '1f61c', 
poop: '1f4a9', 
tongue: '1f61b', 
slightgrin: '1f600', 
grin: '1f603', 
gasp: '1f62e', 
wink: '1f609', 
glasses: '1f60e', 
grumpy: '1f620', 
unsure: '1f615', 
cry: '1f622', 
devil: '1f608', 
angel: '1f607', 
kiss: '1f617', 
winkkiss: '1f618', 
heart: '2764', 
kiki: '1f60a', 
expressionless: '1f611', 
squint: '1f610', 
upset: '1f620', 
persevere: '1f623', 
penguin: '1f427', 
flushface: '1f633', 
crying: '1f62d', 
flushkiss: '1f61a', 
sweating: '1f613', 
like: 'f0000', 
dislike: '1f44e' 
},