Re: Normalisation of filenames
Re: Normalisation of filenames
- Subject: Re: Normalisation of filenames
- From: Quincey Morris <email@hidden>
- Date: Sat, 01 Apr 2017 11:09:40 -0700
On Apr 1, 2017, at 04:41 , Gerriet M. Denkmann <email@hidden> wrote:
>
> for different values of path I got:
> path = @“/ก่ี”; // consonant + mark + vowel → same = YES
> path = @“/กี่”; // consonant + vowel + mark → same = YES
>
> Note: these two paths also look identical in Finder.
>
> I managed to store (using TextEdit) two of these identical looking files in the same folder.
>
> Is this a bug in NSURL or expected behaviour?
What is the behavior that you think is a bug? If I understand correctly, you started from two different path strings, created URLs, and retrieved the path string from the URL. Why is it a bug to get the same path string out again each time?
If your question is about normalization, then there’s no particular reason to think that NSURL does anything about normalizing Unicode strings. That happens in the file system, but NSURL isn’t part of the file system.
In addition, the fact that you created files under the two names suggests that the difference between the strings is not one of normalization. My guess is that your two strings are both grapheme clusters for the same single-grapheme-cluster name, but that the file system have any grapheme cluster “normalization”. The analogy here would be if the Finder displayed all file names in uppercase, even from a case-sensitive volume. You wouldn’t be able to tell “a” and “A” apart, even though they’re different files on disk.
_______________________________________________
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