> On 22 Mar 2017, at 09:05, Alastair Houghton <alast...@alastairs-place.net> > wrote: > > In the context of filesystems (and specifically filenames), the phrases “bag > of bytes” and “bunch of bytes” have a fairly specific meaning. The point is > that the filesystem doesn’t inspect the bytes it’s given, and doesn’t care > what they represent (about the only exception is that it probably doesn’t > support embedded NULs). It isn’t suggesting that the names are treated as an > unordered set of bytes (that’d just be silly). It’s just expressing the fact > that the filesystem doesn’t care what they are - it may compare them, and if > it does so, it will use binary ordering (not some other collation sequence) > and won’t worry about things like case or encoding at all.
That doesn’t sound sensible at all. It means you can create a filename with a byte sequence that isn’t valid UTF-8 and which likely then cannot be accessed by MacOS/iOS processes. It means that you could create multiple files with the “same" name, and that doesn’t sound like a win either. e.g. Aandi’s examples of LATIN SMALL LETTER E (U+0065) COMBINING ACUTE ACCENT (U+0301) and LATIN SMALL LETTER E WITH ACUTE (U+00E9) How can a “next gen” filesystem avoid using Unicode rules when handling filenames? Chris _______________________________________________ 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
