News for hackers. Stuff that matters.
Re:A popular but wrong way to convert a string to uppercase ... by bayindirh on Tuesday October 08, 2024 @10:06AM (#41777526)
I mean, I already know some Unicode internals and linguistics (since I developed a language-specific compression algorithm back in the day), but I have never seen a single character requiring four bytes (and I know Emoji chaining for skin color, etc.).

So, seeing this just moved the complexity of Unicode one notch up in my head, and I respect the guys who designed and made it work. It was not whining or complaining of any sort. :)

Re:A popular but wrong way to convert a string to uppercase ... by fluoridation on Tuesday October 08, 2024 @03:06PM (#41780662)
Cuneiform codepoints are 17 bits long. If you're using UTF-16 you'll need two code units to represent a character.
Re:A popular but wrong way to convert a string to uppercase ... by gpderetta on Wednesday October 09, 2024 @08:25AM (#41787122)
you also need two UTF16 code units for plain emojis.
Re:A popular but wrong way to convert a string to uppercase ... by TorKlingberg on Wednesday October 09, 2024 @09:53AM (#41788005)
Lots of emoji are outside the Basic Multilingual Plane and need 4 bytes in UTf-8 and UTF-16. That's without going into skin color and other modifiers and combinations.