node-unicode / node-unicode/node-unicode-data
`Script_Extensions`: handle unlisted code points
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 154
- Forks
- 18
- Avg merge
- 9h 48m
- Merged PRs (30d)
- 3
Description
All code points not explicitly listed for
Script_Extensionshave as their value the correspondingScriptproperty value.
Ensure this is the case for the generated Unicode data. Currently it looks like we’re ony looking at ScriptExtensions.txt to generate the data.
Contributor guide
No contributing guide indexed for this repository
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 with the generator path that reads ScriptExtensions.txt and the corresponding Script property data, then inspect how the generated Unicode data is assembled. Verify that unlisted code points receive their Script value rather than being omitted, and use the repository's generation or validation workflow to confirm the output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100