>> > It means that the Mac expects file names in UTF-8, and the name "outr
>> > \351" is not a valid UTF-8 string.
Quite the opposite. It shows that Mac OS X will accept arbitrary byte
sequences in filenames. Please do not take up a career in experimental
science.
>> This doesn't explain why the first "touch" works but the latter not.
The first touch works, because on Mac OS X filenames are arbitrary
sequences of bytes.
The second touch fails, because the implementation of the HFS+
filesystem in Mac OS X happens to be limited to UTF-8 filenames.
Please note that this has nothing to do with the Mac OS X kernel
itself -- you'll have similar effects on Linux using a vfat filesystem
mounted ``-o utf8'', and nobody would claim that Linux only accepts
UTF-8 filenames.
Juliusz
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
