-
Notifications
You must be signed in to change notification settings - Fork 573
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::UCD Handle properties that have no code points #23134
base: blead
Are you sure you want to change the base?
Conversation
923f871
to
9b22fca
Compare
lib/Unicode/UCD.pm
Outdated
@@ -4180,7 +4180,9 @@ RETRY: | |||
} # End of loop constructing the converted list | |||
|
|||
# Finish up the data structure for our converted swash | |||
my $type = ($second_try eq 'nfkccf') ? 'ToNFKCCF' : 'ToDm'; | |||
my $type = ($second_try =~ / ^ ( nfkcs?cf ) \z /x) | |||
? 'To' . $1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be 'To' . uc($1)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be better to use the uc
, so I have changed it, thank you. But the tests that failed before this commit in the original form started to pass, so it isn't strictly necesary.
A new property is being added that needs the same special handling as a similar existing one And use \z instead of $ boundary conditions. Spotted by Lukas Mai
This situation had not come up before Unicode 16.0
This has long been done for matching properties. But it has never
happened before Unicode 16.0 that an entire mapping property would have
no code points.