@talkingmoose
Proposals for the #bigfoot #emoji 🫈
https://www.unicode.org/L2/L2024/24251-bigfoot-emoji.pdf

and two #troll emoji 🧌
https://www.unicode.org/L2/L2019/19399-troll-emoji.pdf

https://www.unicode.org/L2/L2019/19232-n5085-troll-emoji.pdf

#Unicode makes all the successful proposals public, and some of them are quite entertaining

@emojipedia’s website keeps track of them under the “Technical” tab 📂

@jdlh @quincy

Among things that cannot be fixed because of stability guarantees are the names of the characters. Still, corrections have been documented as formal name aliases in the NameAliases.txt file in the #Unicode Character Database.

Also, the Unicode Technical Note called "Known Anomalies in Unicode Character Names" hasn't been updated since two years ago; I did submit a report to the UTC, but to no avail...

https://www.unicode.org/notes/tn27/

https://tonton-pixel.codeberg.page/missing-name-corrections-in-utn-27-report-2026-01-18.txt

https://www.unicode.org/Public/UCD/latest/ucd/NameAliases.txt

I thought I'd read that mistakes in #unicode are there forever, but there are errata & corrections!

🤔

https://www.unicode.org/uni2errata/index.html

Anyone know if #rclone normalises a U+FF1A into a U+003A by change?

Looks like the file name was supposed to contain the former but for some reason contains the later. And the later is an illegal character on windows and for some reason trips up some (but not all) windows apps trying to access it from within #wine ...

#unicode