feat: add unicode-3.1.1 #81
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
since we already run build before the test step.
JLHwung
force-pushed
the
add-unicode-3.1.1
branch
from
0588609
to
4ffd81d
Compare
mathiasbynens
approved these changes
Nov 7, 2024
|
Thanks! I’ve set up the new repo + npm publishing workflow + added it to this repo’s README as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added unicode-3.1.1. The Unicode 3.1.1 data is an incremental patch over the Unicode 3.1.0 data, so some resources are from Unicode 3.1.0.
As for the
unicode-3.1.1package, the notable changes fromunicode-3.1.0are that the special casing contexts are different, so as the readme.md and index.js.I would like to see if #1 and #2 can be fixed. After they are fixed we can cut a new release.
Aside: I also added the build step to CI now that the build performance is improved.