-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emoji v12 #20
Comments
+1! Please :) |
Some of the v12 data files don't exist yet, so sadly can't work on this until they are added. Hopefully soon. |
@milesj Ok + looking forward to! Probably not the right "issue" here ... but I really would like to thank you for all your efforts around emojibase! 🙏! Super mega helpful for our OpenMoji project! 🎩 |
Hi @milesj, This is a gentle ping for news :) Any news on v12? Would be super mega helpful to have the update. Sorry to bother you + Many thanks! |
I believe I was blocked on this file: https://unicode.org/Public/12.0.0/ucd/UnicodeData.txt But it looks good to go now. I'll give the build another shot. |
Yay! 👍🙏 |
Hi @milesj, A gentle ping for news :) Any news on v12? Would be super great to have this ready for out of the box use! Sorry to bother you! |
A lot of new stuff was added in the v12 spec, so it isn't an easy upgrade. Will take me quite a bit to get it ready. |
You can view it here: #21 |
Hi, I have generated a script that takes the emojis from http://www.unicode.org/Public/emoji/12.0/ and dumps a JSON with all the content, but I am unable to find the datasource were you get the My script is require 'json'
current_category = ""
category_regex = /# group: ([\w &]+)/
emoji_regex = /([\w ]+) +;+ fully-qualified + #(...*?)([\w :,]+)/
all_emojis = []
File.readlines('emoji-test.txt').each do |line|
if line.include? "# group: "
current_category = category_regex.match(line).captures.first
end
if !line.start_with?("#") && line.include?("fully-qualified")
begin
utf, emoji, name = emoji_regex.match(line).captures
all_emojis << {
:category => current_category,
:name => name.strip!,
:emoji => emoji.strip!,
:hexcode => utf.strip!
}
rescue => error
puts "REGEX ERROR: #{line}"
end
end
end
File.open('emojis-generated.json', 'w') { |file| file.write(JSON.generate(all_emojis)) } |
@raulriera It's a very involved process. All the locale aware data is in CLDR. http://cldr.unicode.org/ |
Hi @milesj, checked out your branch v12 to facilitate the data structure of our upcoming OpenMoji 2.0 release (1. week of May) ... it works + Yay! Quick question: is it safe to use packages/data/en, or will there be more changes? |
@b-g The structure shouldn't change, just the values of the fields. So it should be safe to use for prototyping at the moment. |
Hi @milesj! Sorry to bother you once more! Currently preparing our upcoming OpenMoji 2.0 release for next week ... while doing so, I've spotted that a lot of the |
@b-g Those are official. Direct from the data files: https://unicode.org/Public/emoji/12.0/emoji-test.txt I'm also curious why you're trying to launch with v12 so soon, when iOS/Android/Windows do not support it yet (that I'm aware), and the CLDR data files are still in alpha. Seems a bit premature. |
Only have a handful of errors to fix and this should be ready. Not sure why these are happening though.
|
@milesj Many thanks for the clarification! We will go then with those. (Or when are you planning to fix the open issues above?) OpenMoji is a non commercial project of the HfG Schwäbisch Gmünd (Design University in South Germany), hence we are dependent on the "rhythm" of the semester. In addition we have been working on the project for 2 years and are very keen to have a real production ready set out there (feature complete with a recent Emoji/Unicode version). We had a lot of good feedback ... but people were not using the set in the projects/products as OpenMoji v1 is a bit all over the place in terms of Emoji Versions :) |
Figured it out. It's all the new multi-group skin tone stuff: http://www.unicode.org/reports/tr51/#multiperson_skintones |
Just a bit of polish left and I'll tag an alpha release. |
Yay! Super. Looking forward to the new release! Thanks! |
Hi @milesj, quick feedback:
|
That is how it appears in Unicode now, I ended up creating a list exactly like that CSV and a script to |
Yeah, I don't know what the best course of action for those are yet. v12 added "emoji only" variants, while the variants without I also have no idea how to represent multi-person grouping + skin tones, especially in regards to emoji pickers, since the "parent" emoji will have more than 5 skin tones now, and some of these skin tones are actually 2 skin tones in 1. |
This is "ready". Going to merge the PR and tag an alpha release. Let me know if there are any issues, and if not, I'll tag an official release soon. |
@milesj Yay! In terms of feedback just 👍 and 🙏 from my end! 👀 forward to the alpha release!
+1 makes sense ... just document the decision in the docs |
Ended up doing the reverse: https://milesj.gitbook.io/emojibase/spec#merged-variation-selectors Anyways, alpha releases available! I'll leave this issue open for feedback. |
Tested with twemoji-colr updated to twemoji 12.0.1, seems good so far. Thanks for including the skin tones, means I can remove manually adding them. |
Works for me too! Seems to be a good solution! I think I would add these two comments to make the code example https://milesj.gitbook.io/emojibase/spec#merged-variation-selectors more verbose: {
"annotation": "copyright",
"name": "COPYRIGHT SIGN",
"hexcode": "00A9",
"emoji": "©️", // 00A9-FE0F
"text": "©︎", // 00A9-FE0E
// ...
} |
Good idea! Thanks for the feedback, much appreciated. |
Tagged officials, enjoy! |
Yay! ❤️ ✅ |
http://blog.unicode.org/2019/02/unicode-emoji-12-final-for-2019.html
The text was updated successfully, but these errors were encountered: