> On Mar 22, 2017, at 2:25 PM, davel...@mac.com wrote: > > "Engineering has the following feedback for you: > > iOS HFS Normalized UNICODE names , APFS now treats all files as a bag of > bytes on iOS . We are requesting that Applications developers call the > correct Normalization routines to make sure the file name contains the > correct representation. > > We are now closing this bug report.
If Apple really is making developers responsible for Unicode normalization of filenames, that’s a big compatibility issue and they would need to educate developers, give them sample code, etc. In other words, something that would have been a big deal at last year’s WWDC when APFS was announced. I’m pretty sure that very few developers understand Unicode normalization (I don’t beyond a surface level), so Apple can’t expect them to take it on as an “oh, by the way” sort of thing. Apple takes I18N pretty seriously, and I find it hard to believe that they’d change the filesystem in a way that could potentially cause huge problems accessing files with non-Roman names, without making sure that developers can handle the transition. The above makes me doubt that this is really what’s going on. I’ve worked at Apple, and I know it’s entirely possible that the above quote is the result of a game of ‘Telephone’ in which the actual meaning’s gotten messed up when passed from engineering to tech support. —Jens _______________________________________________ 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
