▲ | simonh 17 hours ago | |||||||
No, no, no, no, no… So then we’d get ‘the same’ character with potentially infinite different encodings. Lovely. Unicode is a coding system, not a glyph system or font. | ||||||||
▲ | kristopolous 16 hours ago | parent | next [-] | |||||||
Fonts are already in there and proto-glyphs are too as generalized dicritics. There's also a large variety of generic shapes, lines, arrows, circles and boxes in both filled and unfilled varieties. Lines even have different weights. The absurdity of a custom alphabet can already be partially actualized. Formalism is merely the final step This conversation was had 20 years ago and your (and my) position lost. Might as well embrace the inevitable instead of insisting on the impossible. Whether you agree with it or not won't actually affect unicode's outcome, only your own. | ||||||||
| ||||||||
▲ | numpad0 9 hours ago | parent | prev [-] | |||||||
macOS already does different encoding for filenames in Japanese than what Windows/Linux do, and I'm sure someone mentioned same situation in Korean here. Unicode is already a non-deterministic mess. | ||||||||
|