On 22 Mar 2017, at 18:00, David Duncan <david.dun...@apple.com> wrote: > > So there was another explanation posted on the bug that I’m not certain you > got, but which I think may explain. > > Basically the concept is that since APFS doesn’t normalize file names, if you > store file names in some other storage (say in your preferences) then what > could happen is this: > > 10.2: File is saved with a file name handed to the file system in NFC form. > File system converts the file name to NFD. You store it as NFC. > 10.3: File system is converted to APFS, and the file name is NFD. You try to > look up the file as NFC, and it fails.
This is going to cause problems, though, when things migrate from HFS+ to APFS, because the HFS normalisation *isn’t* a standard one. In particular, it certainly *isn’t* NFD for the current version of Unicode. The only obvious solution for that would be to have the HFS+ to APFS migration tool *re-normalise* the filenames (maybe it does?), but that’s bound to break things in the (presumably quite common) case where the filename stored in e.g. a plist was originally obtained from the filesystem. Kind regards, Alastair. -- http://alastairs-place.net _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
