←back to thread

108 points liquid99 | 5 comments | | HN request time: 1.043s | source
1. computator ◴[] No.43359743[source]
Just wanted to point out something that not everyone might realize:

Unicode is not supposed to have fonts at all. Unicode defines characters that you can then represent in various fonts. It just so happens that Unicode has many characters that happen to look like the letter "C" (as an example): © for copyright, ℂ for complex numbers (formally called Double-Struck Capital C), etc. The author uses these many variations as a fun way to make "fonts".

replies(2): >>43360060 #>>43360250 #
2. usr1106 ◴[] No.43360060[source]
But Unicode is such a historically grown monster that it violates its own rules in many places.
replies(1): >>43360376 #
3. japanuspus ◴[] No.43360250[source]
If you want to dive into the details, you can copy the "fonted" output to a unicode analyzer. [0] is an online unicode analyzer that seems to work well.

[0]: https://devina.io/unicode-analyser

replies(1): >>43360381 #
4. lifthrasiir ◴[] No.43360376[source]
Is it? Even emoji---one of the most controversial additions ever---was fully justified for its possible accessibility issue when it was introduced in Unicode.
5. antonhag ◴[] No.43360381[source]
I often reach for jq to understand what unicode is in a string, e.g.:

  [wl-paste|xclip-o|pbpaste] | jq -R --ascii-output
It doesn't provide any per-character explanation, but it is local and I already have jq installed.