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

61–70 of 254 posts

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

#61

Post by vintermann »

lmkg wrote: post #9
kratom_sandwich wrote: post #2

I love this character and I love the fact that is being updated. Just to get this right: at some point some person chose to doodle the letter instead of writing it the correct way and now we have a corresponding Unicode character? Sort of amazing and it also makes you think ...

There was a... "tradition" is a strong word, perhaps "trend" is better. Authors making copies of the Bible or related works in Cyrillic, that the letter O (equivalent to Roman O) at the beginning of the word for "eye" would be stylized to look like an eye. There are a variety of glyphs along these lines: Ꙩ, Ꙫ, Ꙭ. All of them, including ꙮ, were added to Unicode as a single group. The glyph "ꙮ" was used to refer to an…

Hah, and here I thought I was making a joke when I called it a biblically accurate O!

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

#63

Post by reaperducer »

koboll wrote: post #30
etamponi wrote: post #4

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

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.

One historical use in the 1400s doesn't merit a character and never did

One known and surviving use. It is possible that it exists in other places, since the vast majority of the planet's written work has not been digitized. It may also have been used other places that have not survived.

Just because it's not important to you does not mean it is not important.

The fact that is survived for 600 years makes it interesting and worth saving. It is infinitely unlikely that anything you do, write, or say will last that long.

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

#64

Post by runarberg »

koboll wrote: post #30
etamponi wrote: post #4

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

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.

idk. when the word Planet was redefined such that Pluto was no longer a planet, it kind of ruined the word Planet. It suddenly wasn’t nearly as useful as a word as it used to (even though now it has a precise meaning). For most people that use the word, it won’t matter (and is actually rather exciting) that they keep discovering new planets in our solar system.

If they’d treat the word characters the same way, it would only serve to confuse and do no favors to the remaining glyphs.

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

#65

Post by koala_man »

bityard wrote: post #51
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…

Today, I wrote a document by hand containing a new symbol that only looks like genitalia if you squint really hard. Where do I apply to have it included in unicode so that it can be digitized properly?

Can you reuse 𓂸 or 𓂺?

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

#66

Post by skyyler »

djur wrote: post #47
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…

Unicode doesn't have a character for every illuminated initial, nor should it. I'm not clear on why this character should be considered any differently.

http://std.dkuug.dk/jtc1/sc2/wg2/docs/n3194.pdf

It was introduced with other "ocular O"s which are seemingly more commonly used than this one.

It's not quite an illuminated initial.

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

#67

Post by lucumo »

bityard wrote: post #51
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…

Today, I wrote a document by hand containing a new symbol that only looks like genitalia if you squint really hard. Where do I apply to have it included in unicode so that it can be digitized properly?

Rule-lawyering wise-asses try to mess with many policies. It's rarely a sensible indictment of a policy, nor is it very effective. Anyone dealing with such people just ignores them.

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

#68

Post by dhosek »

This is not exactly a correct description. Unicode does not specify the appearance of characters, only their meaning. It seems what’s changed is the reference presentation of the character in the Unicode tables, not the character itself. Unicode goes to great lengths to preserve backwards compatibility so changing the meaning of a code point would violate that principle. Your OS or application providing Unicode 15.0.0 support will not change the appearance of U+A66E. The appearance is dependent on the font.

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

#69

Post by modzu »

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…

why isnt the artist formerly known as prince in unicode?
Post reply on HN