Comment by foxfluff
4 years ago
> The Unicode people veered off the tracks and sank into a swamp when they decided that semantic information should be encoded into Unicode characters.
As if that weren't enough, they also decided to cram half-assed formatting into it. You got bold letters, italics, various fancy-style letters, superscripts and subscripts for this and that.. all for the sake of leagacy compatibility. Unicode was legacy right from the beginning.
The "fonts" in Unicode are meant to be for math and scientific symbols, and not a stylistic choice. Don't use them for text, as it can be a cacophony in screen readers.
Unicode chose to support lossless conversion to and from other encodings it replaces (I presume it was important for adoption), so unfortunately it inherited the sum of everyone else's tech debt.
Unicode did worse than that. They added code points to esrever the direction of text rendering. Naturally, this turned out to be useful for injecting malware into source code, because having the text rendered backwards and forwards erases the display of the malware, so people can't see it.
Note that nobody needs these code points to reverse text. I did it above without gnisu those code points.
Yeah, where do you stop when you start adding fonts to Unicode?
If #include <𝒸𝓊𝓇𝓈𝒾𝓋𝑒.h> is wrong, I don't want to be right.
𝐼 𝘭𝘪𝘬𝘦 𝑢𝑠𝑖𝑛𝑔 𝐛𝐨𝐥𝐝 𝑎𝑛𝑑 𝘪𝘵𝘢𝘭𝘪𝘤 𝑡𝑒𝑥𝑡 𝑗𝑢𝑠𝑡 𝑡𝑜 𝒎𝒆𝒔𝒔 𝑤𝑖𝑡ℎ 𝑎𝑛𝑦𝑜𝑛𝑒 𝑤ℎ𝑜'𝑠 𝑡𝑟𝑦𝑖𝑛𝑔 𝑡𝑜 𝑢𝑠𝑒 𝑡ℎ𝑒 𝑠𝑒𝑎𝑟𝑐ℎ 𝘧𝘶𝘯𝘤𝘵𝘪𝘰𝘯 𝑖𝑛 𝑡ℎ𝑒𝑖𝑟 𝑏𝑟𝑜𝑤𝑠𝑒𝑟 𝑜𝑟 𝑒𝑑𝑖𝑡𝑜𝑟. Sᴍᴀʟʟ ᴄᴀᴘs ᴡᴏʀᴋ ғᴏʀ ᴀ sɪᴍɪʟᴀʀ ᴇғғᴇᴄᴛ. ℑ𝔱 𝔤𝔢𝔱𝔰 𝔢𝔵𝔱𝔯𝔞 𝔣𝔲𝔫 𝔦𝔫 𝔯𝔦𝔠𝔥 𝔱𝔢𝔵𝔱 𝔢𝔡𝔦𝔱𝔬𝔯𝔰 𝔴𝔥𝔢𝔯𝔢 𝔶𝔬𝔲 𝔠𝔞𝔫 𝔪𝔦𝔵 𝔲𝔫𝔦𝔠𝔬𝔡𝔢 𝔰𝔱𝔶𝔩𝔢𝔰 𝔞𝔫𝔡 𝔯𝔢𝔞𝔩 𝔰𝔱𝔶𝔩𝔢𝔰. pᵁrⁿoͥvͨiͦdͩeͤs oͤpⁿpͩoˡrͤtˢuˢnities cᶠoͦnͬfusing aᵖnͤdͦᵖˡᵉ sͭoͪfͤtͥwͬare.
Use Markdown if you want italics.
We have emojis so we’re probably not far from Unicode characters that blink.