(The discussion is on a personal Github repository created by Christoph Päper, who appears to be an actual participant in the W3C standards process but I cannot find evidence he is formally involved with the Unicode Consortium in any way. It appears Päper is maintaining this repository for public information purposes, or possibly gathering community opinions which he will later submit to Unicode formally through the public comment process.)
And the ultimate bloging begins
- she/her
28 / autistic / Toronto
nekoweb
amikumanto.nekoweb.org/neocities
amikumanto.neocities.org/You must log in to comment.
in reply to @mcc's post:
instead of dedicating an entire code point to the cool S maybe we could use a 😎—ZWJ—U+0083 sequence
we had a twitter thread (i know, i know) unexpectedly pop off about this very topic back in 2022, which actually got engagement from various Unicode committee members (and assorted linguists): https://x.com/EXJoyces/status/1572733371972980739
i still would love to see the cool S included by unicode but i suspect it won't happen due to the structure of their guidelines for inclusion 😔
The thing that gets me about multiocular O is that it was used one time in one text and somehow that was enough
My favourite part is the fact they messed up the first time so there's actually 2 different characters for it now.
One codepoint, just two variants of the glyph. I think most fonts that actually have the glyph use the old version with the incorrect number of eyes.
So is ☫, only on flags. The Unicode Consortium has a history of making questionable decisions.