Skip to content

Updating with Unicode 17, bumping version to match: 17.0.0#10

Closed
ad08fee3 wants to merge 2 commits intojobiewong:masterfrom
ad08fee3:master
Closed

Updating with Unicode 17, bumping version to match: 17.0.0#10
ad08fee3 wants to merge 2 commits intojobiewong:masterfrom
ad08fee3:master

Conversation

@ad08fee3
Copy link

This repo is a little out of date :)

I figured this would be some fun practice. Let me know if you see any issues with the results.

Also, I was thinking having the version number match the unicode standard would be a good idea.

emojilib changed the format of their json file, which is why the parsing logic slightly changed.

Also adding requirements.txt for ease of installation.

@ad08fee3 ad08fee3 marked this pull request as ready for review November 26, 2025 00:07
@ad08fee3
Copy link
Author

ad08fee3 commented Nov 26, 2025

Welp I'm now realizing that https://github.com/muan/emojilib is actually still on Unicode 16. So this should probably be using 16 as well.

In fact, you could probably scrap this if you wanted.

@jobiewong
Copy link
Owner

Thanks so much for contributing! You are right I have neglected this repo for a few months. I will check over your changes and decide what the best way forward is for versioning of this package. If emojilib has fallen behind the Unicode standard then perhaps this project will have to use another method for pulling keywords.

@ad08fee3
Copy link
Author

I'm actually working on a new espanso package that you may be interested in. :)

It's not done yet, but it is functional if you want to experiment:

https://github.com/ad08fee3/espanso-emoji-picker

It looks like muan/emojilib: Emoji keyword library. is closely related to muan/unicode-emoji-json: Emoji data from unicode.org as easily consumable JSON files.. The latter has a PR up to update it to 17: Updates for Unicode 17.0 by forresto · Pull Request #21 · muan/unicode-emoji-json
So maybe emojilib 17 will come soon after that.

In any case, the Espanso package that I am working on pulls from both of those locations instead of scraping the Unicode site, for better or worse.

@ad08fee3 ad08fee3 closed this Jan 4, 2026
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