Re: console translator set without encoding
Danilo Segan <firstname.lastname@example.org> writes:
> What are you going to do when you come across a filesystem where you
> have two files with such names which only differ in normalisation form
> used (i.e. fully decomposed or fully composed)? Yeah, you can ensure
> that no filesystem created via GNU/Hurd is going to have such
> instances, but what about filesystems created elsewhere?
> Are you going to treat such filesystems as erroneous?
> Filenames are 8-bit ASCII compatible strings (UTF-FS as in
> "filesystem-safe" originally), and that's all you need to know to make
> POSIX-compliant programs.
This unfortunately fully depends on the filesystem. Or do you mean
the interface to the filesystem?