Make sure all emoji are fully qualified
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 53
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
we may want to make sure all emoji in emoji are fully qualified. This is more complex than just having an emoji presentation selector at the end. Sometimes it is in the middle, such as for 2764 FE0F 200D 1F525 ❤️🔥.
Data at https://www.unicode.org/Public/17.0.0/emoji/emoji-test.txt. More succinct data which seems to only contain fully-qualified and component entries: https://unicode.org/emoji/charts/emoji-ordering.txt.
Currently, two emoji are not even valid: See: https://github.com/typst/codex/pull/167#issuecomment-4447816396.ast should be 002A FE0F 20E3 and hash should be 0023 FE0F 20E3. They are both missing U+20E3.
I am not sure whether we actually want to do that. I am opening this issue now to make sure I don't forget to look into it later.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the entries in the emoji data against Unicode 17.0.0's emoji-test.txt or emoji-ordering.txt, paying particular attention to qualification sequences with selectors in the middle. The issue is done when the intended qualification policy is decided and the affected entries match it, including any required U+20E3 sequences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- content
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100