4 ms·
There is way more than enough wacky stuff introduced by Unicode. Having dozens of letters A, for example. And giving a Japanese Kanji character the same code as
by ncmncm 7y ago
There is way more than enough wacky stuff introduced by Unicode. Having dozens of letters A, for example. And giving a Japanese Kanji character the same code as a Chinese one that usually looks similar.
- mehrdadn 7y agoThat might be wacky to you but I'm not sure it's wacky to the people to whom it makes a difference.
- ncmncm 7y agoLots of the wacky stuff came from the original dream of a purely 16-bit code, and then more wacky stuff to extend it from there. I.e., starting from UTF-8 could have avoided any amount of unpleasantness. But of course UTF-8 wasn't invented until later. The 16-bit representation got encrusted in OSes and languages of a certain period. The same goes, of course, for writing systems, going back to the first, that we would all do differently in hindsight. Even today we are making apparently sensible choices we (or our digital successors) will regret as deeply. ISO 8601 looks good now, but it only delays the transition to a rational calendar which, admittedly, we would certainly get wrong if we tried codifying one today. Fortunately daylight saving time will be gone worldwide before the next decade passes, but not without some places getting stuck at the wrong timezone. (E.g. Portugal different from Spain, and probably Indiana different from itself.)
- kevin_thibedeau 7y agoIndiana doesn't have special time zones any more. It allows individual counties to choose which standard zone to be in but they all observe the normal DST.
- jrochkind1 7y agoUnicode did not introduce having dozens of letters A, they existed without unicode. Unicode just gives you a way to represent them -- and bonus, often to normalize them all to a normal letter A too. It is a mistake to think that Unicode has the ability to people's text behavior by not supporting things. I mean, maybe it does now that it's so popular, but in order to get adoption it had to support what people were actually doing. People had use cases to put "𝔄" adn "A" in the same document and keep them distinct without unicode. It is not a service for unicode to refuse to let them; and if it tried, it would just lead to people finding a way to do it in a non-standardized or non-unicode-standardized way anyway, which still wouldn't help anyone. You might just as well say "I don't understand why we need lowercase AND capital letters, the standard is just complicating things supporting both -- the ancient romans didn't need two cases after all"
- deleted 7y ago[deleted]
- tomp 7y agoThere's no way to distinguish "A" "uppercase a" and "Α" "uppercase α" in written text, but they're different Unicode letters (and might be rendered differently depending on font).
- sansnomme 7y agoYeah, that is quite inconsistent. Kanji literally means "Chinese Character" so it should be the same for the letter A. Unless a French A isn't equivalent to an English A.
- Shorel 7y agoCyrillic А is not the same as English A. For example, some fonts render A in a way that looks like Cyrilic Л. (Like The Mandalorian title screen.) This would be incorrect if using the same A for both: https://i.ytimg.com/vi/V8fC7bdV-mI/maxresdefault.jpg https://i.ytimg.com/vi/V8fC7bdV-mI/maxresdefault.jpg
- bonoboTP 7y agoI don't see anything special in the linked image. The As look as they would in Latin script. (probably not what you meant, but just in case: the fourth letter is not a Cyrillic A but a D.)
- GrantSolar 7y agoI think the image is not meant to show the problem but show a case where if the Cyrillic A had been stylised the same way that the English A is in the English version, the two distinct letters would become indistinguishable such that the Cyrillic title would effectively read "The Mlndlloriln"
- bonoboTP 7y agoI see, for those out of the loop, the English title screen does not have the horizontal bar in the As.
- deleted 7y ago[deleted]
- Shorel 7y agoI should have linked the English title as well, now I read my comment and see it is not sufficiently unambiguous. Here: https://en.wikipedia.org/wiki/File:The_Mandalorian_logo.jpg https://en.wikipedia.org/wiki/File:The_Mandalorian_logo.jpg you can see that the A letters are rendered the same as Cyrillic Л. To further the confusion, in Buenos Aires there are many street signs that use Л as the letter A, and they use П as the letter N.
- msla 7y ago> There is way more than enough wacky stuff introduced by Unicode. Having dozens of letters A, for example. You'd have to go back before Unicode to prevent this. Unicode was created with certain engineering constraints, one of them being round-trip compatibility. This means that it needs to be possible to go from $OTHER_ENCODING -> Unicode -> $OTHER_ENCODING and get a result which is bitwise-identical to the input. In short, Unicode is saddled with the fact pre-Unicode text encoding was a mess, plus the fact people tend to not like irreversible format changes.