On Monday, May 21, 2012 3:23:55 PM, Mattias Pantzare wrote: >> Therefore, I'm in favor of normalizing file names to precomposed form in the >> Mac version of the AFS client, since it would fix both halves of the >> problem, and we wouldn't have to wait for Apple to change the behavior of >> Mac OS X (if they are going to do so at all). > > I am working on doing this in the afs client. Limited testing is very > promising but I will panic the kernel sometimes. > > Contact me privately if you are interested in testing my fix. > > Apple will not fix this on their end, the recommend that filesystems > fix this. I think that Apple is right.
The Windows client does perform file system based normalization. When the subject of applying normalization rules to the UNIX clients there was a strong objection because unlike on Windows where all file systems are UNICODE, on UNIX the file system has no concept of a character set. All file names are simply octet streams that are interpreted by the application according to the active Locale. And it is possible for each process to have a different locale. As a result, a file system that applies UNICODE normalization to all file names will break many existing applications.
signature.asc
Description: OpenPGP digital signature
