3 ms·
As I understand, it's actually more or less the rule that same glyphs that are semantically different - e.g. letters in different alphabets - are represented by
by int_19h 7y ago
As I understand, it's actually more or less the rule that same glyphs that are semantically different - e.g. letters in different alphabets - are represented by different codepoints. One exception was made for CJK, and that because they were trying to fit everything into the 16-bit space that Unicode had at the time. And that exception was itself extremely controversial.
- gumby 7y agoSince I remember these debates as they unfolded: an existing code block for various alphabets was typically used for, as I said, round trip compatibility and what was seen at the time as reduced complexity for migrating old code. “Han unification” was caught bitterly and the lack of alphabetic unification was cited by opponents that the motivation was racist. I have a strong opinion as to how Han unification should or should not have been conducted, if at all, however I recognize the strength of the counter argument as well so to avoid flame wars I don’t express my opinion. Given that this comment is a deep reply to a reply and probably will never be seen this shows how hot tempers flared at the time, and perhaps still do.
- gumby 7y agos/caught/faught/ but saw it mere moments too late to change