Skip to content

feat: support InPC and InSC#99

Merged
mathiasbynens merged 1 commit into
node-unicode:mainfrom
JLHwung:indic
Jun 13, 2026
Merged

feat: support InPC and InSC#99
mathiasbynens merged 1 commit into
node-unicode:mainfrom
JLHwung:indic

Conversation

@JLHwung

@JLHwung JLHwung commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Closes #57

@mathiasbynens

Copy link
Copy Markdown
Collaborator

LGTM!

I’m curious, what’s your specific motivation for adding support for these?

@mathiasbynens mathiasbynens merged commit 79d6f0e into node-unicode:main Jun 13, 2026
1 check passed
@1ec5

1ec5 commented Jun 13, 2026

Copy link
Copy Markdown

For what it’s worth, this will be very useful for MapLibre to detect viramas in order to correct the behavior of the ICU segmenter when segmenting text by grapheme cluster.

@JLHwung

JLHwung commented Jun 13, 2026

Copy link
Copy Markdown
Contributor Author

Nguyễn is right. The node-unicode-data is used by MapLibre.

I think eventually we may just export all data from UCD. IMO the #14 is no longer relevant because thanks to the encoded ranges, the unicode-17.0.0 package is only 1.9MB extracted, way smaller than the the size 108MB of then unicode-6.3.0 package.

@mathiasbynens

Copy link
Copy Markdown
Collaborator

IMO the #14 is no longer relevant because thanks to the encoded ranges, the unicode-17.0.0 package is only 1.9MB extracted, way smaller than the the size 108MB of then unicode-6.3.0 package.

I agree.

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.

Consider add Indic Syllabic Category (UISC) and Indic Positional Category (UIPC)

3 participants