News for hackers. Stuff that matters.
Re:Unicode is harder than you think by sedatk on Tuesday July 25, 2023 @08:14PM (#36871487)
Windows used to use UCS-2 because UTF-16 hadn't been invented yet. Any Windows after Windows 2000 supports UTF-16.

You can't just dismiss the whole operating system API space just because NTFS doesn't enforce filename encoding. Yes, you might encounter file names with invalid UTF sequences because some app might be allowing them to be created. That can also happen in Linux too. Then add Linux, and probably others to the list. Then, what's the use for this list?

Re:Unicode is harder than you think by kzrdude on Tuesday July 25, 2023 @08:56PM (#36871807)
On Linux it's at least explicit that file paths can be any string of bytes (any or "no" encoding)
Re:Unicode is harder than you think by sedatk on Wednesday July 26, 2023 @05:56PM (#36885684)
I don't understand why this gets brought up. You still have to assume the filenames are encoded to something in order to display them, otherwise there would be no way to display a filename other than in hexadecimal. Windows always uses UTF-16 while Linux uses the locale (which defaults to UTF-8). It's not like working with filenames on Linux is somewhat easier or more straightforward, it's certainly not.