>If you have a filesystem that forces NF-D, then I would say its a >poorly designed filesystem that makes such choices, because its >way to low level to care about things like that. Filenames should >be "string of bytes",
Filenames are _names_. They are names for _human_ use; computers would be just as happy passing about inode numbers. Humans don't like dealing with strings of bytes. They like dealing with strings of characters, and you'll note that almost every filename created by humans make sense as strings of characters - in fact, even filenames created by the computer tend to be strings of graphic characters from the ISO-646-INVARIANT set. It appears that due to historical considerations, Unix systems consider filenames strings of bytes, but I consider that a malfeature; no system desgined today would make the same mistake, and I would be that if Unix had been designed to be a multilingual system from the start, such a design would never had existed. (The XCCS or ISO-2022 might be hardcoded in, though.) -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
