-
Notifications
You must be signed in to change notification settings - Fork 770
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
Support Unicode 15.1 new GB9c break rule #1718
Comments
PR welcome. |
I have recently tried doing a naive upgrade to the latest unicode standard, but have seen that the tests are failing.
Thanks for tracking this down. I have stopped at the previous step, because I was busy. In case you do want to contribute: https://github.com/ycm-core/ycmd/blob/master/cpp/ycm/Word.cpp#L31 |
@DonKult I am afraid I am having troubles understanding the new rule. Up to now the boundary rules table contained only break properties that were explained in the values table. Now that GB9c is added, it talks about "Indic_Conjunct_Break" ( On top of that,
EDIT: Found it!
Now, this is a new property. That means we will need to extend our EDIT2: I understand the point of having links to the versioned documents in I know, I know... I am to blame for that mess. |
We have merged the update. |
ycmd embeds its unicode support files and tests (currently for version 13), but a script (
update_unicode.py
) is provided to update to the latest unicode version. This used to work to upgrade to version 14, but doesn't anymore with 15. The tests fail for example with:The reason is that 15.1 introduces a new rule for (not) breaking: GB9c and of course the new tests exercising this rule fail now.
Prior art implementing this rule elsewhere: JuliaStrings/utf8proc#253
Would be nice if support for newer Unicode standards could be added to ycmd.
The text was updated successfully, but these errors were encountered: