Skip to content

Conversation

@JuanitoFatas
Copy link
Contributor

@JuanitoFatas JuanitoFatas commented Jun 1, 2019

🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧

Working Pull Request in order to keep up with Twemoji upstream.

The first step is to have all the names from Unicode data.

When this work is done, archive https://github.com/jollygoodcode/emoji-keywords, which was a scrappy solution looking at now 🤦‍♂

Unicode 12.0 data: https://unicode.org/Public/emoji/12.0/
CLDR 35.1: http://unicode.org/Public/cldr/35.1/

🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧

ED-17a. qualified emoji character — An emoji character in a string that (a) has default emoji presentation or (b) is the first character in an emoji modifier sequence or (c) is not a default emoji presentation character, but is the first character in an emoji presentation sequence.

ED-18. fully-qualified emoji — A qualified emoji character, or an emoji sequence in which each emoji character is qualified.

ED-18a. minimally-qualified emoji — An emoji sequence in which the first character is qualified but the sequence is not fully qualified.

ED-19. unqualified emoji — An emoji that is neither fully-qualified nor minimally qualified.

http://www.unicode.org/reports/tr51/tr51-16.html

using easier to understand Dir instead of git command
The Rakefile is defined under lib/tasks/db.rake.

Necessary files will download from https://github.com/unicode-org/cldr,
and save in vendor folder under cldr release version folder.

- parse emojis from cldr release, version can be changed at emoji_data_files.

The emojis are from emoji_test.txt (starting from release-32)

and keywords (names) are from cldr annotations and annotationsDerived.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants