-
Notifications
You must be signed in to change notification settings - Fork 443
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
Trying to reference the Cf category generates an error #719
Comments
This is fixed in |
This was referenced Mar 12, 2021
jorickert
pushed a commit
to jorickert/regex
that referenced
this issue
Aug 1, 2022
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. Fixes rust-lang#835 Related rust-lang#719 b1489c8
jorickert
pushed a commit
to jorickert/regex
that referenced
this issue
Aug 1, 2022
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. Fixes rust-lang#835 Related rust-lang#719 b1489c8
BurntSushi
pushed a commit
that referenced
this issue
Mar 4, 2023
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. So when going through the canonicalization process, it would get normalized to 'Script' before being checked as a general category. We fix it by special casing it. See also #719 Fixes #835, #899
BurntSushi
pushed a commit
that referenced
this issue
Mar 5, 2023
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. So when going through the canonicalization process, it would get normalized to 'Script' before being checked as a general category. We fix it by special casing it. See also #719 Fixes #835, #899
BurntSushi
pushed a commit
that referenced
this issue
Mar 21, 2023
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. So when going through the canonicalization process, it would get normalized to 'Script' before being checked as a general category. We fix it by special casing it. See also #719 Fixes #835, #899
BurntSushi
pushed a commit
that referenced
this issue
Apr 15, 2023
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. So when going through the canonicalization process, it would get normalized to 'Script' before being checked as a general category. We fix it by special casing it. See also #719 Fixes #835, #899
BurntSushi
pushed a commit
that referenced
this issue
Apr 17, 2023
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. So when going through the canonicalization process, it would get normalized to 'Script' before being checked as a general category. We fix it by special casing it. See also #719 Fixes #835, #899
BurntSushi
pushed a commit
that referenced
this issue
Apr 17, 2023
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. So when going through the canonicalization process, it would get normalized to 'Script' before being checked as a general category. We fix it by special casing it. See also #719 Fixes #835, #899
BurntSushi
pushed a commit
that referenced
this issue
Apr 17, 2023
'sc' refers to the 'Currency_Symbol' general category, but is also the abbreviation for the 'Script' property. So when going through the canonicalization process, it would get normalized to 'Script' before being checked as a general category. We fix it by special casing it. See also #719 Fixes #835, #899
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I use the unicode class
cf
:It generates this error:
But I see the format is here in the code:
https://github.com/rust-lang/regex/blob/master/regex-syntax/src/unicode_tables/property_values.rs#L72
If I change the regex to be
\p{Format}
then it actually works. This is a little confusing to me, can someone please explain why\p{cf}
doesn't work?The text was updated successfully, but these errors were encountered: