-----BEGIN PGP SIGNED MESSAGE-----
AFAICS, all of the case folding mappings in Unicode 3.1 map to a
string that is normalised according to NFC or NFD in the same way
as the input character, don't map to a different combining class,
and operate uniformly on canonical equivalents. Also any combining
characters following a character that is mapped will stay in the
same order. Therefore, I conjecture that:
casefold(NFC(x)) = NFC(casefold(x))
casefold(NFD(x)) = NFD(casefold(x))
for all of the case folding types and all strings x. However,
CaseFolding-4.txt says, "NOTE: case folding does not preserve
normalization formats!"
It clearly doesn't preserve NFKC or KFKD (U+20A8 RUPEE SIGN demonstrates
how this can fail), but if it does preserve NFC and NFD, shouldn't that
be clarified? Or have I missed something, and there is some reason why
it doesn't preserve NFC/NFD?
- --
David Hopwood <david.hopwood@zetnet.co.uk>
Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5 0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
iQEVAwUBO9zBHDkCAxeYt5gVAQHbPQgApl2UZe0JlQHYzJB5C8V6RK2UvF3LXIHx
/MAxM6KjmkZozWrb9nkMA0NxT3BpehPMrJOUM49xRoLvwcFzLK5vwOwVyOVpZZXw
rqa2CmymDAJfvCoCEH4nOGXqLwezZdVFQuHgJsxAaUTIQWLd5bcwB8dCB5VEd4Yz
J8Qrx53q3p5+TO+jWk2dgUeOhr3G5W2Kf6zka8NeFGlL5HhTpwT2agQM5vii14/s
JnC8Ka+HNbkDdPLNio6iOR44h46MLrr8jyO4oGWk/SX16KT5ATUxdNNjCD7jjrPF
mGhIQywClkIjgtQy4JYWhyxrQknvMih2f/ausbRn4ldf9FBtk33DNQ==
=6tSm
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2.1.2 : Sun Oct 28 2001 - 21:30:07 EST