Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unicode 9.0 support - regenerate UNF tables and test data #24

Closed
wants to merge 2 commits into from
Closed

Unicode 9.0 support - regenerate UNF tables and test data #24

wants to merge 2 commits into from

Conversation

nomoon
Copy link
Contributor

@nomoon nomoon commented Mar 2, 2017

I cloned the base unf project, updated the Unicode source files and regenerated normalization-test.txt from official Unicode 9.0 data (CompositionExclusions.txt DerivedNormalizationProps.txt UnicodeData.txt NormalizationTest.txt), and regenerated the definitions and tables using the lisp utilities.

Here I've provided a PR containing the new Unicode 9.0-compatible table.hh and normalization-test.txt in the form unf expects. It passes all of the tests included (18,722 entries in the new 9.0 test, up from 18,136 in master), and I have double-checked (with some benchmarking code from another normalization gem of mine) that this also passes a test using the unmodified official NormalizationTest.txt.

@nomoon
Copy link
Contributor Author

nomoon commented Mar 2, 2017

Looks like the changes have been accepted upstream.

@nomoon
Copy link
Contributor Author

nomoon commented Apr 9, 2017

Conflicts are due to type signedness changes in 8a6a735 to fix #15. Resolving should be as simple as integrating those into the new file, or pulling the latest table.hh from upstream and doing the same.

@knu
Copy link
Owner

knu commented Apr 11, 2017

Done in 1033f48, thanks!

@knu knu closed this Apr 11, 2017
@knu
Copy link
Owner

knu commented Apr 11, 2017

Oops, I didn't realize this was a PR, went ahead and imported the files myself. I've added a merge commit for future reference.

@nomoon
Copy link
Contributor Author

nomoon commented Apr 11, 2017

No problem, thanks for updating it! This is by far the fastest normalization gem so it's nice that it supports 9.0 now :)

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