3 ms·
> the problem is caused by Unix allowing any character in filenames (other than slash and null). Most Unixes don't allow any character; they allow any byte oth
by toast0 6y ago
> the problem is caused by Unix allowing any character in filenames (other than slash and null).
Most Unixes don't allow any character; they allow any byte other than ascii slash or zero. Turning bytes into characters is outside the scope of most Unix kernels and the filesystems therein.
- skissane 6y ago> Turning bytes into characters is outside the scope of most Unix kernels and the filesystems therein. All the major contemporary Unix(-like) kernels do have code in them to do file path charset translation. It is very important when dealing with removable media (ISO-9660, UDF), FAT filesystems, network filesystems (especially CIFS/SMB, but even some NFS implementations), filesystems defined in terms of Unicode such as NTFS, HFS+, APFS. Traditional Unix filesystems don't do this, but they were originally designed at a time when few clearly distinguished the concept of byte from the concept of character.