On 16 Jan 2013, at 17:40, Quincey Morris <quinceymor...@rivergatesoftware.com>
wrote:
> On Jan 16, 2013, at 09:12 , "jonat...@mugginsoft.com"
> <jonat...@mugginsoft.com> wrote:
>
>> To be honest I rarely remember to call -fileSystemRepresentation.
>> The docs seem to indicate that its only purpose is to replace abstract / and
>> . characters with OS equivalents.
>> On OS X this would have seem to have no net result.
>>
>> Is there more to this?
>
> You absolutely have to do it. There may be other things, but the
> transformations in 'fileSystemRepresentation' include at least:
>
> 1. '/' characters are replaced by ':', for file systems that use '/' as a
> path component separator. (':' has always been illegal in file names at the
> UI, so the transformation is reversible.)
>
> 2. Graphemes with multiple Unicode representations are converted to a normal
> form, for file systems that store Unicode file names. (Can't remember which
> form -- Unicode normal form D, I think.) That removes indeterminacy when
> there are accented "characters" (graphemes) with equivalent 1- and 2-
> character Unicode forms, or "characters" with multiple accents where the
> order of the accents could vary.
If you ever sample -fileSystemRepresentation, you'll see it just calls through
internally to -[NSFileManager fileSystemRepresentationWithPath:], which
documents the unicode handling a little better:
> A C-string representation of path that properly encodes Unicode strings for
> use by the file system.
_______________________________________________
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
