> On Apr 1, 2017, at 11:58 AM, Gerriet M. Denkmann <gerri...@icloud.com> wrote: > > I think that the examples above show, that NSURL does indeed do something > about normalising Unicode strings.
That makes sense; I’d expect that one of the RFCs covering URLs describes normalization. Otherwise constructing URLs (for a REST API, say) could become quite ambiguous because you wouldn’t know which way to encode various Unicode characters. > But my point is that NSURL gets the normalisation wrong in this case; or at > least that it is not very consistent in normalising strings. Yes, it does seem wrong that you can have two filenames that are treated as distinct by the filesystem, but whose URL.path properties produce identical NSStrings. Presumably if you use NSFileManager or NSURL to iterate the contents of that directory, you get the same filename twice? That seems pretty unambiguously wrong. (I assume you’ve been following the recent thread here about potential Unicode problems with the APFS filesystem in iOS 10.3? It sounds like things might become even more confusing.) —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
