Of course, the way to fix *nix filenames in the first place is, well, not to use a ham-fisted definition of filenames in the first place.
But that would be too difficult. Also, it abrogates Freedom. In this specific case, it abrogates the freedom to use spaces in filenames, which (for some ungodly reason, possibly to do with the real world) users want.
Bit of a bugger when your entire shell pipeline depends upon a stream-o-bytes, innit?
“It’d be easier and cleaner to write fully-correct shell scripts if filenames couldn’t include any kind of whitespace. There’s no ...