On Nov 5, 2005, at 15:31:58, Juliusz Chroboczek wrote:
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 bytesequences in filenames. Please do not take up a career in experimentalscience.
Thanks; I'm a theoretical scientist. No problem there. We don't jump to conclusions from experimental facts, we predict what experimentalists should see...
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.
Thanks for the explanation. I had to read it several times to understand your point: The operating system part that handles files consists of two layers, Mac OS X and HFS+. The upper layer accepts all byte sequences (up to limitations with "/" and "\000", probably), and the lower layer handles only UTF-8. (One of the two -- probably also HFS+ -- is also case insensitive.)
-erik -- Erik Schnetter <[EMAIL PROTECTED]> My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from www.keyserver.net.
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
