News for hackers. Stuff that matters.

A comment on Database character sets and collations explained – why utf8 is not UTF-8. Parent comment

Re:Database character sets and collations explained – why ut... by erik_seaberg on Thursday January 06, 2022 @06:47AM (#29822416)
If 21 bits seems like an odd place to stop, it’s because the Unicode consortium said they wouldn’t allocate any codepoints beyond U+10FFFF (the end of plane 16), because that’s as far as UTF-16 could go using a four-byte surrogate pair (10+10 bits, offset by U+10000).
[ Parent | on HN ]
Re:Database character sets and collations explained – why ut... by Dylan16807 on Thursday January 06, 2022 @11:25PM (#29834822)
Not that UTF-8 really stops at 21. As originally formulated it has 5 and 6 byte encodings for 26 and 31 bits, but an entire unsigned int of code points was later decided to be unnecessary, and those encodings were marked as invalid.
[ Parent | on HN ]
Re:Database character sets and collations explained – why ut... by Dylan16807 on Saturday January 08, 2022 @03:01AM (#29849668)
* Positive signed int, not unsigned, oops.
[ Parent | on HN ]