Re: [SOLVED] Re: FSCopyObjectASync Not Calling Callback In Cocoa

FROM : Clark Cox
DATE : Thu May 01 19:48:21 2008

On Thu, May 1, 2008 at 10:43 AM, stephen joseph butler
<stephen.<email_removed>> wrote:
> On Thu, May 1, 2008 at 12:03 PM, Matt Long <matt.<email_removed>>
>  wrote:
>
>
>  > Stephen Butler pointed out that I need to use -[NSString
>  > fileSystemRepresentation]. I have switched to this and it works. I not real
>  > familiar with this call, but it looks like it's working. I'll look into why
>  > this is the better choice. I'm just not familiar.
>
>
>  For almost all intents and purposes, it returns UTF-8,


It returns UTF-8, but with a very specific Unicode composition:
<http://developer.apple.com/technotes/tn2002/tn2078.html#HowEncoded>

>  because that's what
>  the APIs to HFS+, et al expect. However, it's conceivable that some file
>  system might want path strings in another (legacy) format. Say, Shift_JIS,
>  Big5, or KOI8-R.


When you think about this, it is really not possible, as
fileSystemRepresentation works on any string, including those that do
not represent existing files. There is no way to know, in general,
which filesystem a particular path will live on.

>
>  I'm not sure any do. I'm not even sure the vfs layer allows the fs to
>  register a preference. But there's a function for it, so you might as well
>  use it.




--
Clark S. Cox III
<email_removed>