Date: Thu, 10 Jul 2025 17:24:24 -0700
On Thursday, 10 July 2025 17:07:08 Pacific Daylight Time JJ Marr wrote:
> "For each string S containing only assigned characters in a given Unicode
> version, toCasefold(toNFKC(S)) under that version is identical to
> toCasefold(toNFKC(S)) under any later version of Unicode."
Did you understand the part about NFKC? Even if you did, will every user of
the API? Will that be acceptable for all users? Because it may not be - for
example, file names for Apple operating systems (which are usually case-
insensitive) are usually presented in NFD, not NFC or NFKC.
And even if we agree this is good enough for everyone, what of other
operations, transformations and property queries in the Unicode standard?
> "For each string S containing only assigned characters in a given Unicode
> version, toCasefold(toNFKC(S)) under that version is identical to
> toCasefold(toNFKC(S)) under any later version of Unicode."
Did you understand the part about NFKC? Even if you did, will every user of
the API? Will that be acceptable for all users? Because it may not be - for
example, file names for Apple operating systems (which are usually case-
insensitive) are usually presented in NFD, not NFC or NFKC.
And even if we agree this is good enough for everyone, what of other
operations, transformations and property queries in the Unicode standard?
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel Platform & System Engineering
Received on 2025-07-11 00:24:26