Hello Erik, On Wed, May 07, 2008 at 03:04:25AM +0200, Erik Dalén wrote: > On Wed, May 7, 2008 at 12:30 AM, <[EMAIL PROTECTED]> wrote: > > Applying encodings to file names (treating them as text as opposite to > > byte sequences) is broken fundamentally - this can _not_ be done properly. > > > > Well, the bug is really in Mac OS X, the issue is if we should have a > workaround for it or not. Could file a bug with apple and with luck > they'll fix it in 10 years. Or we could normalize the file names in > the mac clients.
It is not a bug, it is wrong design. Windows and MacOS X behave differently but this does not mean any of them is "buggy". It means both of them did wrong, in incompatible ways, so that the wrongdoing did not compensate :) (I can imagine yet another system which does and/or will do file name encoding in its own way and become "Windows- and MacOS-incompatible" as well.) I do not think Posix is perfect, but at least on this point it did it right, file names consist of bytes not characters. Best regards, Rune _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
