On 9/1/09 2:55 PM, Kyle Sluder said: >> That might be the best approach, depending on all the usual things. But >> 'high-ASCII' filenames have been acceptable on the Mac for a very long >> time, and do work. > >The problem is that the encoding used in the string literal might not >be that used on disk.
Perhaps I'm misunderstanding, or need to learn something new here, but I don't get it. If you create a file using a Cocoa API you'll be passing an NSString. The NSString knows the encoding. Cocoa knows how to convert any NSString to whatever encoding the POSIX layer wants. Where is the problem? Are you worried about the encoding of text files passed to the compiler? Use UTF8. -- ____________________________________________________________ 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
