Unicode character “ꙮ” (U+A66E) is being updated

Post by lifthrasiir » Tue, Sep 20, 2022, 3:43 AM UTC

lmm wrote: post #217

lifthrasiir wrote: post #197

Earlier quoted context omitted.

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.

Post by gumby » Tue, Sep 20, 2022, 4:13 AM UTC

ArchD wrote: post #214

gumby wrote: post #149

Earlier quoted context omitted.

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.

Post by Tagbert » Tue, Sep 20, 2022, 5:04 AM UTC

just-ok wrote: post #224

From the tweet’s image: > written in an extinct language, Old Church Slavonic It’s absolutely not extinct and is used by the Eastern Orthodox Church in their religious texts almost exclusively. It’s taught to children alongside their Sunday school curriculum and, of course, in seminaries.

Post by Someone » Tue, Sep 20, 2022, 6:01 AM UTC

thaumasiotes wrote: post #173

anthk wrote: post #171

Earlier quoted context omitted.

Cent is easy to grasp if you speak a Romance.

But it doesn't combine with ops. You'd need to talk about a hecatops or a hecatontops. And even more than it can't combine with ops, it can't combine with clops because there is no such root.

Post by hoseja » Tue, Sep 20, 2022, 8:12 AM UTC

bobsmooth wrote: post #165

tzs wrote: post #122

Earlier 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.