mcc on Nostr: There's this really awkward issue where the next major revision of Unicode is Unicode ...
There's this really awkward issue where the next major revision of Unicode is Unicode 16, but it's almost impossible to search for because search engines of any kind invariably correct searches for "Unicode 16" or "Unicode 16.0" to searches for "UTF-16", which is a 16-bit *encoding* of Unicode, because UTF and Unicode are synonyms right? I'm almost wondering if they should have pulled a Microsoft Windows 9 and skipped directly from Unicode 15 to Unicode 17 or maybe just Unicode 2024.
Published at
2024-07-15 23:49:03Event JSON
{
"id": "af51cf7d519634b2513e2b61fa0edad81917e4d2a9ff35b6d3eba1fc9abd37cd",
"pubkey": "a3162b9720f6b515ac4bd22d5ea4abf0f85f5685130dca40f46fe684fe85b255",
"created_at": 1721087343,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/mcc/statuses/112793180119140172",
"activitypub"
]
],
"content": "There's this really awkward issue where the next major revision of Unicode is Unicode 16, but it's almost impossible to search for because search engines of any kind invariably correct searches for \"Unicode 16\" or \"Unicode 16.0\" to searches for \"UTF-16\", which is a 16-bit *encoding* of Unicode, because UTF and Unicode are synonyms right? I'm almost wondering if they should have pulled a Microsoft Windows 9 and skipped directly from Unicode 15 to Unicode 17 or maybe just Unicode 2024.",
"sig": "6bdb1e0397cfcf99d0acaeed868406361503466641fbbcfc7121849a654f92e62ba7878f0da6c7fb3d558e8279aa7f60502b8ded75035dcfdeb34b296cc8a8d8"
}
