111–120 of 254 posts
Here[1][2] is the scan of manuscript from 1429, image #251 [1] https://lib-fond.ru/lib-rgb/304-i/f-304i-308/#image-251 [2] https://web.archive.org/web/20110927102700/https://www.stsl....
Quoted post unavailable.
I guess because the goal of Unicode is to be able to represent every character that's appeared in language. This one is in a published book, while guns and a sexual intercourse symbol aren't. Emoji was a weird value add that Japanese mobile providers added to their phones before Unicode. To get them to move to Unicode, they had to keep them. That's why there's a Tokyo Tower emoji, but not an Eiffel Tower. That's why…
By the same reasoning, the 7-eyed O has now been used more than once, so it deserves a glyph! So the right way to do this is to introduce a new character for the correct glyph, and also leave the current one (perhaps changing the title). Otherwise these tweets won't make when read by someone that updated to Unicode 15.0
Make a new character!
Earlier quoted context omitted.
Unicode basic rule is that character definitions never ever change, even when enumerated erroneously.
Yes, but this is a change either way, because that codepoint's definition referred to that character. Either the reference or the description of the appearance has to change.
ꙮ ꙮ
ꙮ ꙮ ꙮ
ꙮ ꙮ
Make a new character. Updating the existing character ruins the meaning of all previous usages.
It's like trying to change an API. Don't disrespect your existing users. Make a new version.
(ꙮ ͜ʖꙮ)
Think of all the ASCII art this botches. That has to have some historical importance to the Unicode standards body.
(⌐ꙮ_ꙮ)
For scholarly digital (unprinted) documents where the correct character rendering matters, erroneous past usages can be trivially found with grep, a date search, and easily corrected. The domain experts will familiarize themselves with this issue and fix the problem. Don't take a shotgun to it!
This message wꙮn't have the ꙮriginally intended meaning if the characters are updated from underneath.
ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ ꙮ
Earlier quoted context omitted.
For as inclusive as that mission is, it seems weird to me how limited in certain areas unicode is. For instance, people use peach emoji since there isn't one for butt, eggplant since there's no penis, etc. This doesn't contradict the stated goal exactly, but it seems against the spirit of it at least.
One could argue that emoji should have never been added to Unicode in the first place. Peaches and butts are images, pictures, illustrations, whatever - but they are not characters. There's no writing system which has a colored drawing of a peach as a character.
Earlier quoted context omitted.
Uff. I'm not sure we have space for another glyph in Unicode. Looks pretty packed in here...
UTF-8 is still more than 80% empty, and can be potentially extended...
Sadly, ꙮ is not eligible for engraving by Apple on AirPods.
I don't understand why this character needs to exist given that, at least according to the author, it has only been seen once in the wild, and it's semantically identical to another more widely used character. I'm glad I'm not responsible for unicode. Clearly I have the wrong mindset for it.
Wait a minute, how will we refer to the old glyph in the future? Once this is updated the articles such as this one will have the new shape.
[1] https://twitter.com/BabelStone/status/1323440365429542919