Why is NSString->FSRef so hard?
Why is NSString->FSRef so hard?
- Subject: Why is NSString->FSRef so hard?
- From: Erg Consultant <email@hidden>
- Date: Sat, 25 Apr 2009 16:33:35 -0700 (PDT)
I am trying to convert an NSString containing a path to a file directly to an FSRef. If there are no special characters in the path, it's easy - I can go from NSString to CFURL to FSRef.
But if the path contains any special characters at all, both CFURL and NSURL creation routines fail. No matter what I do, or which routines I use, it won't work.
Unfortunately I am stuck with some 3rd party apps that have special characters like (tm) in their bundle names and I can't change them.
Isn't there some easy way to get an FSRef from an NSString that is a path containing special characters?
Thanks,
Erg
_______________________________________________
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