On 6/1/09 3:03 PM, Martin Wierschin said: >>> const UInt8* utfPath = (UInt8*)[path UTF8String]; >>> OSStatus err = DetermineIfPathIsEnclosedByFolder >>> (kOnAppropriateDisk, kTrashFolderType, utfPath, false, &inTrash); >> >> For the archives: 2 more problems: >> >> a) use fileSystemRepresentation not UTF8String. > >I initially considered that, but the documentation for >DetermineIfPathIsEnclosedByFolder specifically says it requires UTF-8 >encoded characters, while fileSystemRepresentation mentions no >guarantee as to the encoding.
Nice catch. >I'm sure that that the file system >representation is currently UTF-8, and will stay that way, but I >don't want to make that assumption. > >I don't often work with the C-based APIs, so maybe I'm way off base >here. Should I file a documentation bug? And if so, which piece of >documentation needs adjusting? I'd say it's DetermineIfPathIsEnclosedByFolder's docs that could use clarifying. But at least they say _something_ about encoding, unlike the man pages for open() and friends. :) But it's not a huge issue: fileSystemRepresentation and UTF8String give the same thing 99% of the time. -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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
