But how do we opt out of the update!
Use a font that contains the previous glyph. This is just an update to the reference glyph, and there is nothing prevents you from using a font that has an upside-down A in the place of U+0041.
Unicode character “ꙮ” (U+A66E) is being updated
211–220 of 254 posts
Re: Unicode character “ꙮ” (U+A66E) is being updated
#212When my kids were young, I accidentally flubbed the pronunciation of "Santa Claus" once and said something that sounded a lot like "Centiclops", which I decided to roll with. Centiclops is a lot like a cyclops with one eye, except the as a reading of the roots clearly indicates, this is a creature with 100 eyes. Today I learn that Centiclops effectively has a Unicode character. As Centiclops' representative in the wo…
Greek mythology actually did have a "centiclops" -- Argus Panoptes ("all eyes"), who had a hundred eyes all over his body. Hera assigned him to watch over Io, a nymph who had been turned into a cow, so that Zeus wouldn't come and shag her in secret. Argus was slain by Hermes (a Zeus loyalist); to mourn and honor him, Hera had his eyes transferred to the peacock's tail.
The real Greek for a hundred-eyed being would be something like "hekatonoptes", but Argus wasn't called that as far as I know.
Re: Unicode character “ꙮ” (U+A66E) is being updated
#213Earlier quoted context omitted.
It's in place of "goo" in "mnogoočimi" (many-eyed) in the phrase "many-eyed seraphims", so it at least makes sense.
my Old Church Slavonic is pretty rusty (well, nonexistent), but "mnogo" looks like modern Russian много (many), and the -imi I guess would be instrumental plural like -ими? but Russian for "eye" is глаз or око. I'm guessing oč -> око, and it's a compound word? or is the č an infix, something like "ogo" is eye, and mnogoočimi is such because the two -og-s (one from mnog and the other from go) fuse because "mnogoögočim…
Pretty sure it is mnogo-oči-tii. The word "oči" still means "eyes" (although mostly in poetry).
Re: Unicode character “ꙮ” (U+A66E) is being updated
#214I’m not sure how I feel about this. I’m not an expert by any means. But something just doesn’t feel right when you’ve got unicode with a character with one known use from forever ago. Doesn’t this open up the flood gates to just a ridiculous amount of work or else biased gatekeeping? How much work would it be to implement your own font of the entire unicode set? Or is that not actually a thing and fonts implement as-…
There are quite a few such characters in Unicode because academic articles about things like cuneiform need to be digitized too. And because the historical record is so sparse, we often have vanishingly few, or only one example of a character, and perhaps no way to know if it was a misprint or a real character. Actually this character seems like a scribe's joke, no different from the illustrated characters at the beg…
Why don't those digitized articles just use images? They can have any variant of any glyph they want to document.
Re: Unicode character “ꙮ” (U+A66E) is being updated
#215Since this link list https://slatestarcodex.com/2017/05/09/links-517-rip-van-link... , the character has become somewhat of a meme in the appropriate circles. Not surprised it's getting some love at last.
Re: Unicode character “ꙮ” (U+A66E) is being updated
#216Personally I'm waiting for Kaktovik numerals in unicode.
Re: Unicode character “ꙮ” (U+A66E) is being updated
#217Earlier quoted context omitted.
Meanwhile one still can't roundtrip regular Japanese without some kind of funky out-of-band signalling. By itself this kind of thing is harmless, but it speaks to poor prioritization from Unicode.
This is incorrect. I think you defined round-trip as something else, but some character set A providing a round-trip compatibility with other set B means that B can be converted to A and back to B without a loss. And it is one of Unicode's explicit goals to provide a round-trip compatibility with major encodings including Japanese ones. Han unification only means that when you convert Japanese encodings (B) to Unicod…
By that logic any 8-byte encoding is round-trip compatible with all encodings, since however bad the mojibake is, if you know what the original encoding was then you can always just convert back to that.
Re: Unicode character “ꙮ” (U+A66E) is being updated
#218Personally I'm waiting for Kaktovik numerals in unicode.
Aren't they there already? 𝋀𝋁𝋂𝋃𝋄𝋅𝋆𝋇𝋈𝋉𝋊𝋋𝋌𝋍𝋎𝋏𝋐𝋑𝋒𝋓 Or do you mean waiting for more fonts to support them?
Re: Unicode character “ꙮ” (U+A66E) is being updated
#219Cut & paste from the pdf: многочитїй.
Hmmm. Well, on my screen, it’s lips/kiss. A Unicode fail.
Re: Unicode character “ꙮ” (U+A66E) is being updated
#220Earlier quoted context omitted.
If that was once its mission, it was clearly abandoned long ago. They rejected Klingon characters on the grounds that it has low usage for communication, and that many of the people who do communicate in Klingon use a latinized form. ꙮ seems to just be a fancy way of writing О. I haven't seen anything that says it has a different meaning. The arguments for excluding Klingon seem to apply even more so to ꙮ.
Unless it's legitimately someone's native tongue, conlangs shouldn't be in unicode. If there are kids out there that are native Klingon speakers, then you can make the argument it should be included.
so all you need is one crazy parent? shouldn't be too hard to find