News for hackers. Stuff that matters.

A comment on How UTF-8 Works. Parent comment

Re:How UTF-8 Works by colejohnson66 on Tuesday February 08, 2022 @12:04PM (#30261003)
UTF-16*, not UCS-2. Although there are probably many programs that assume UCS-2.
[ Parent | on HN ]
Re:How UTF-8 Works by mark-r on Tuesday February 08, 2022 @12:59PM (#30261921)
When Windows adopted Unicode, I think the only encoding available was UCS-2. They converted pretty quickly to UTF-16 though, and I think the same is true of everybody else who started with UCS-2. Unfortunately UTF-16 has its own set of hassles.
[ Parent | on HN ]
Re:How UTF-8 Works by account42 on Wednesday February 09, 2022 @06:17AM (#30271396)
Technically, they converted to WTF-16 [0] since many places, including filenames, allow you to use unpaired surrogates.

[0] https://simonsapin.github.io/wtf-8/

[ Parent | on HN ]
Re:How UTF-8 Works by nwallin on Tuesday February 08, 2022 @03:51PM (#30264521)
Note that the asterisk in `UTF-16*` is a really big asterisk. I fixed a UCS-16 bug last week at my day job.
[ Parent | on HN ]
Re:How UTF-8 Works by WorldMaker on Tuesday February 08, 2022 @07:53PM (#30267143)
Yeah, there's sometimes a lot more hacks like WTF-8 and WTF-16 in practice on UCS-2 originally systems (including Windows and JS) than is healthy: https://simonsapin.github.io/wtf-8/
[ Parent | on HN ]