This is the stupidest design decision even by 90s standards: "NTFS allows any sequence of 16-bit values for name encoding"
Conversation
This Tweet was deleted by the Tweet author. Learn more
Replying to
It is but at least you don't have transcoding and endianness issues.
1
8
Is filenames being encoded in unknown and not stored encoding not a transcoding issue? If you actually want to show them to people it sure is.
Just use UTF-8 or provide a mechanism to specify the encoding for esoteric cases. It's not a rocket science.
1
We aren't speaking about hypotheticals but the real world. I'd say NTFS/Windows being able to at least render well-formed filenames is better than the *nix world where you can't even do that. I get reminded of this every time I try extracting a japanese zip from the 90s on Linux.
2
Show replies