We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I noticed an odd case in JuliaLang/julia#52408 (comment):
julia> using Unicode: normalize julia> s = "J\uf72\uec8\u345\u315\u5bf\u5bb\U1d16d\u5b0\u334\u35c" "J" julia> normalize(s, casefold=true) == normalize(normalize(s), casefold=true) false julia> normalize(normalize(s, casefold=true)) == normalize(normalize(s), casefold=true) false
(The Julia Unicode.normalize function calls utf8proc, and defaults to NFC normalization.)
Unicode.normalize
utf8proc
Not sure if this is a bug or just a weird behavior of Unicode. Would be good to try it out with ICU or some other library.
The text was updated successfully, but these errors were encountered:
I get something similar in Python 3:
>>> import unicodedata >>> s = "J\u0f72\u0ec8\u0345\u0315\u05bf\u05bb\U0001d16d\u05b0\u0334\u035c" >>> unicodedata.normalize("NFC", s.casefold()) == unicodedata.normalize("NFC", s).casefold() False >>> unicodedata.normalize("NFC", s.casefold()) == unicodedata.normalize("NFC", unicodedata.normalize("NFC", s).casefold()) False
So I guess this is a weird quirk of Unicode?
Sorry, something went wrong.
isequal_normalized("בְּ", Unicode.normalize("בְּ")) == false
That's quite unfortunate. Seems like exactly the kind of thing the Unicode Consortium is supposed to think through and avoid.
No branches or pull requests
I noticed an odd case in JuliaLang/julia#52408 (comment):
(The Julia
Unicode.normalize
function callsutf8proc
, and defaults to NFC normalization.)Not sure if this is a bug or just a weird behavior of Unicode. Would be good to try it out with ICU or some other library.
The text was updated successfully, but these errors were encountered: