Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

twitter.com

Post reply on HN
Print view View original

231–240 of 254 posts

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

#231

Post by hoseja »

yakireev wrote: post #108
kadoban wrote: post #107

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.

You can have entire sentences constructed out of emoji.

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

#232

Post by pbhjpbhj »

kadoban wrote: post #107
colejohnson66 wrote: post #41

Earlier quoted context omitted.

Unicode's mission is to make every document "roundtrip-able". Even if a character is only used once, it should be possible to save a plaintext version of the containing document without losing any information. Roughly, I should be able to put a transcription of that one translation from the 1400s on Wikisource without using images. You may disagree with me, and that's fine, but it doesn't change Unicode's mission. Be…

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.

I thought peach was a vulva. What's the emoji for a vulva then?

Don't tell me Presidents of the United States' song "Peaches" was about butts!?

https://en.wikipedia.org/wiki/Peaches_(The_Presidents_of_the...

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

#233

Post by josefx »

lmm wrote: post #158
colejohnson66 wrote: post #41

Earlier quoted context omitted.

Unicode's mission is to make every document "roundtrip-able". Even if a character is only used once, it should be possible to save a plaintext version of the containing document without losing any information. Roughly, I should be able to put a transcription of that one translation from the 1400s on Wikisource without using images. You may disagree with me, and that's fine, but it doesn't change Unicode's mission. Be…

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.

To be fair they wanted to keep everything representable with 16 bits and that wasn't going to happen without the Han-unification. The mess when everything still had to move to a 32 bit representation has been far reaching, many programming languages went from exposing code points atomically as "char" to some half encoded nonsense value that just happens to also be a valid standalone value in UTF-16 most of the time and a source of bugs when you least expect it.

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

#234

Post by sloonz »

colejohnson66 wrote: post #41
koboll wrote: post #30

Earlier quoted context omitted.

Honestly it probably deserves the Pluto treatment: decertification as a character. One historical use in the 1400s doesn't merit a character and never did.

Unicode's mission is to make every document "roundtrip-able". Even if a character is only used once, it should be possible to save a plaintext version of the containing document without losing any information. Roughly, I should be able to put a transcription of that one translation from the 1400s on Wikisource without using images. You may disagree with me, and that's fine, but it doesn't change Unicode's mission. Be…

> so what harm is there in one codepoint no one will ever need?

Fonts bloat (do you want a font with 1 million characters in it ? I don’t. Do you want to have to install 1000 fonts having 1000 characters each to be sure to cover all the Unicode table ? I don't).

Lots of issues for everyday programmers (how do you handle weird unicode characters in your validation code ?) potentially leading to security issues (bypassing validation rules by close-but-different characters, phishing…)

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

#235

Post by partomniscient »

jerf wrote: post #26
tempodox wrote: post #21

Earlier quoted context omitted.

“Santa Clause” would translate to “holy clause”. There might be such a thing but I think you meant Santa Claus :)

My fingers love adding the e's on the end of any worde that can conceivably take them. Also have that problem with any word that can take an "ly" even if I don't meanly it. Fixed, thanks.

That's supercalifragilisticexpialidociously strangee.

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

#236

Post by MonkeyClub »

tzot wrote: post #90
doodpants wrote: post #32

Earlier quoted context omitted.

Or perhaps this character is an accurate representation of a Dekaclops.

It'd be dekaops, because the -cl- is part of “cy cl e”+“ops” (one round eye, with the one dropped because it's inferred). So “cycle” out, “deka” in.

I thought ops was from opsis and referred to a “circle-like face”?

Like oinops, referring to the “wine-like face” (ie dark read) of a sea passage in the evening.

May be wrong, though, I don’t have my tools handy to check now.

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

#237

Post by chickenimprint »

aasasd wrote: post #163
diimdeep wrote: post #24

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

So the text at that point literally talks about ‘many-eyes seraphims’. The eyes symbol is a pure gag—seems to be spliced in place of the letter ‘о’ in the word ‘eye’ just a little down the line. (However, Old Slavonic is a tough read due to no spaces, so I'm not sure about that word. But at least it's not the Glagolitic script, which was just ridiculous and actually had multi-circle letters.)

As far as I can tell it swallows up the preceding го.

It seems to be preceded by other jocular glyphs among scribes. A regular o received a central dot when writing the word "eye": ꙩ

Words containing "two" or "both" had an o replaced by two conjoined os: ꚙ

It is only natural to carry on the in-joke for the dual and plural "eyes" like this: ꙭ

Our scribe simply got a little excited, following the pattern to it's logical end point in the term "many-eyed"

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

#238

Post by kadoban »

pbhjpbhj wrote: post #232
kadoban wrote: post #107

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.

I thought peach was a vulva. What's the emoji for a vulva then? Don't tell me Presidents of the United States' song "Peaches" was about butts!? https://en.wikipedia.org/wiki/Peaches_(The_Presidents_of_the...

I'm not sure if there is one. Or maybe it's used for both, depending on context/community?

The song was definitely a vaginal reference as far as I ever knew.

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

#239

Post by jerf »

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.

The thing that will annoy you most of all is that I was fully aware of all of this at the time... and I did it anyways.

Truly the purity of English will never recover from the trauma that I have inflicted on it.

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

#240

Post by rhplus »

colejohnson66 wrote: post #41
koboll wrote: post #30

Earlier quoted context omitted.

Honestly it probably deserves the Pluto treatment: decertification as a character. One historical use in the 1400s doesn't merit a character and never did.

Unicode's mission is to make every document "roundtrip-able". Even if a character is only used once, it should be possible to save a plaintext version of the containing document without losing any information. Roughly, I should be able to put a transcription of that one translation from the 1400s on Wikisource without using images. You may disagree with me, and that's fine, but it doesn't change Unicode's mission. Be…

By the original reasoning, shouldn’t every fancy illuminated character from medieval manuscripts get its own codepoint?
Post reply on HN