One other thing I should mention - the mangled char in question is the tm symbol (option-2). In its string form, the debugger shows it as the tm char.
But when I convert the string to an NSURL using fileURLWithPath, and then do a CFShow, the tm is converted to *three* hex chars: %E2%84%A2 Are NSURL and CFURL not toll-free bridged? Erg ________________________________ From: Sean McBride <cwat...@cam.org> To: Erg Consultant <erg_consult...@yahoo.com>; cocoa-dev@lists.apple.com Sent: Sunday, April 26, 2009 2:41:20 PM Subject: Re: Why is NSString->FSRef so hard? Erg Consultant (erg_consult...@yahoo.com) on 2009-04-25 7:33 PM said: >Isn't there some easy way to get an FSRef from an NSString that is a >path containing special characters? You can use NDAlias: <http://github.com/nathanday/ndalias/tree/master> It provides an NSString category that converts to/from FSRef. Sean _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
