APFS
APFS
- Subject: APFS
- From: Quincey Morris <email@hidden>
- Date: Thu, 15 Jun 2017 23:57:57 -0700
FWIW, the WWDC session on APFS is worth watching:
https://developer.apple.com/videos/play/wwdc2017/715/
<https://developer.apple.com/videos/play/wwdc2017/715/>
because it relates to an inconclusive discussion we had recently about iOS file
names with normalization issues “breaking” existing apps.
If I understand it correctly, Apple has abandoned the ridiculous idea of making
iOS APFS normalization-sensitive (that is, of treating strings differing only
in normalization as different file names). Specifically:
— macOS APFS will be natively normalization-insensitive from the get-go, as
originally planned
— current iOS APFS volumes will have normalization insensitivity imposed on
them at a level above the file system, starting in iOS 11(?)
— at some future time, iOS APFS will become natively normalization-insensitive,
presumably involving a conversion step on existing volumes
However, the new native normalization is not the current, broken, non-standard
normal form from last century that HFS+ uses, but proper Unicode 9
normalization form D. There seems to be some future-proofing, in case the
normalization rules change again in a later version of Unicode, but nothing was
said about how that might work.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden
- Follow-Ups:
- Re: APFS
- From: Ken Thomases <email@hidden>