On Monday, May 21, 2012 4:25:41 PM, Mattias Pantzare wrote: > Mac OS X is not UNIX in this case. Applications start working by doing this. > > This is as apple recommends: > https://developer.apple.com/library/mac/#qa/qa1173/_index.html
Yet, Apple does not apply these recommendations to the Apple NFS implementation for exactly the same reasons as I described. Personally I have no issue with assuming that OSX always produces UTF-8. I would like the conversion to always store the file names in pre-composed form. It is important to be able to handle the cases where the path components read from the file server are not UTF-8 in any form or contain illegal character sequences. While I personally have no objection, there were very strong objections from the AFS user community back in 2008 when this subject was most recently debated. The conclusion at the time was that the existing directory interfaces are arbitrary octet strings but in the future a new set of directory manipulation RPCs could be created that require pre-composed UTF-8. Jeffrey Altman
signature.asc
Description: OpenPGP digital signature
