3 ms·
> What's your definition of "compact" here? Number of elements in an encoding 5: ˜ n o ñ õ 3: ˜ n o > so I worry you'd end up with something closer to a vec
by eviks 3y ago
> What's your definition of "compact" here?
Number of elements in an encoding
5: ˜ n o ñ õ
3: ˜ n o
> so I worry you'd end up with something closer to a vector format than a normal character encoding.
then stop 1 step before that :)
- lifthrasiir 3y agoMuch easier said than done. Try to actually do that. A good start would be IDS.TXT I've linked above; this gives about 500 approximately atomic characters to start with [1]. Now extend this to the entirety of Ideographic Variation Database [2], which tries to solve the most cited problems with Han unification. And then add some kind of semantic annotation as you've suggested (I have no idea, maybe you have a better idea). [1] 123 components that are already encoded, 121 components ({01}, ...) that are partial characters, ~123 "unpresentable" components (?), and ~115 "minor" variations (〾) that may require additional components or two. [2] https://unicode.org/ivd/ https://unicode.org/ivd/
- eviks 3y ago> Much easier said than done. Try to actually do that Ha-ha, thanks for the offer, but I'll pass - all that complexity is precisely why I'm not even going to try, it requires a lot of dedicated team effort put into it, a simple "try" is doomed to fail.
- Dylan16807 3y agoI worry that "1 step before that" requires a database of information about how to actually put the pieces together for a huge fraction of characters. And that without the database it doesn't work right, and with the database it's like the current system with extra steps and extra layers of complicated abstraction. You'd be able to encode some novel characters but that's a high cost.