At 14:52 01/10/24 +0900, Soobok Lee wrote: >Mark and Martin and Doug, > >Case mapping / NFC /NFKC tables are already freezed up and will >remain unchanged forever even with future newly added scripts ???? > >There is no need to modify or upgrade all the tables?
There may indeed be a need to upgrade some of the tables. For casing, you usually would add both lower and upper case at the same time, and add that to the table. The way nameprep is currently designed, the lower case form of the new characters could be used with old client software. There would be a need for a client upgrade to use uppercase letters from the new script. This seems to be a reasonable tradeoff. But anyway, as far as I know, the scripts in the pipeline are single-case only, so this is only theory. For NFC, there is the change that e.g. some new precomposed character is added. This chance is very low because the Unicode consortium is on record that it won't do it. But assume it happens; assume q-cedilla get's added. Then what would happen is that a decomposition q-cedilla -> q, cedilla gets added to the big data file, and in addition, q-cedilla gets added to the so-called composition exclusions. Now an old application will only know about q and cedilla and will use these to represent the combination. A new application may know about the new character q-cedilla, but it would then also know how to normalize that, and because of the composition exclusion, it would normalize to q, cedilla, i.e. stay decomposed. So in both cases, you get the same decomposed result. Regards, Martin.
