Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by saurik on Monday May 06, 2024 @01:54AM
(#40271545)
I don't understand why these are part of Unicode. Were they ever used as part of text? Why Pac-man but no Donkey Kong? What is the logical basis for this set?
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by saurik on Monday May 06, 2024 @01:21PM
(#40277001)
Let me be more specific: I don't understand why pac-man and fragments of chess pieces and race cars or alienate--essentially all of these sections of "game sprites", which is what jumped out at me as they dominate the first page of this proposal--are being included in Unicode. I do understand why the various block drawing characters used in teletext schemes should be included.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by lifthrasiir on Tuesday May 07, 2024 @06:38AM
(#40284081)
Because they provide a round-trip compatibility with those character sets, which have been one of the defining goals of Unicode from the very beginning. The same reason that various ornaments and dingbats and even emojis did end up in the Unicode.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by eviks on Monday May 06, 2024 @04:08AM
(#40272335)
For all those groups-of-4 pacmans symbols wouldn't it be better to have a single pacman and a rotation angle adjustment? (then you also wouldn't be limited to just 4)
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by ygra on Monday May 06, 2024 @07:19AM
(#40273339)
Unicode in general doesn't like encoding arbitrary markup unless absolutely necessary. And for historical character sets the scope is limited and finite, so just using four code points is much easier than trying to specify a higher-order meaning for certain sequences of code points. Unicode also doesn't like encoding things based on hypothetical future use.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by kalleboo on Monday May 06, 2024 @08:20AM
(#40273767)
I'm actually surprised that the TeleText ones weren't already in Unicode, as TeleText is still live and in use in many parts of Europe[0], so being able to encode those in modern software is still relevant if you want to produce, edit or archive tele-text content.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by Joker_vD on Monday May 06, 2024 @11:38AM
(#40275898)
Oh my god, do we need yet another slightly differently looking font for the basic Latin alphabet in the Unicode? I guess I can use them for the keywords in my next world-disrupting programming language, but still: don't we have like, at least 8 fancy fonts already? Could we get at least a second Greek alphabet instead, pretty please?
The symbols for electronic circuits and sprites are fine though. I particularly appreciate the right-facing fish with open mouth.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by esbranson on Monday May 06, 2024 @03:27PM
(#40278567)
NFKC (Compatibility Decomposition, followed by Canonical Composition) has been my go-to for this, due to this exact issue that was messing with the normal NFC. Twitter of all places was using some other bizarre Unicode range for bold characters.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by dlachausse on Monday May 06, 2024 @05:48PM
(#40279880)
I'm personally shocked at all the negativity in the comments so far about this.
As someone who is terrible at creating graphics, I love the breadth of what is available in Unicode. Plus, these Unicode graphics allow for creative, beautiful, and fun terminal apps to be created that are in the spirit of the hacker ethos.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by knuckleheadsmif on Monday May 06, 2024 @09:24PM
(#40281309)
I was part of Unicode effort it’s inception at Xerox and then Apple. It has drifted so far from the initial core principles (that happened a very long time ago) that I find Unicode as a whole a technical embarrassment. Seeing yet another duplicate range of latin characters that are just a font variation sickens me to my core even forgetting all the other issues with this range. This is exactly the kind of standard that exemplifies the problems in designing by committee. There are no true guiding principles.
Re:Unicode 16: Symbols for Legacy Computing Supplement [pdf]
by nxobject on Thursday May 09, 2024 @05:21AM
(#40306513)
I agree - considering Han unification, what justifies the existence of the segmented digits or the outline uppercase characters? (Or traditional vs simplified Chinese characters, etc etc etc…)
Specifically https://www.unicode.org/L2/L2019/19025-terminals-prop.pdf covering, among others, all the teletext characters.
Though I'd also like to see more terminal emulator programs with integrated graphics support.
[0] e.g. Sweden https://www.svt.se/text-tv/100 https://www.svt.se/text-tv/401
The symbols for electronic circuits and sprites are fine though. I particularly appreciate the right-facing fish with open mouth.
As someone who is terrible at creating graphics, I love the breadth of what is available in Unicode. Plus, these Unicode graphics allow for creative, beautiful, and fun terminal apps to be created that are in the spirit of the hacker ethos.