site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Oct 1, 2008, at 1:43 AM, Jonas Maebe wrote: More information is available at: http://developer.apple.com/qa/qa2001/qa1173.html http://developer.apple.com/qa/qa2001/qa1235.html - Kevin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... What is the extent of the interaction between the current locale setting (as in the LANG, LC_TYPE, etc environment variables) and the encoding expected/returned by posix functions such as open(), stat() etc? Are they always to be encoded using the current LC_TYPE, always using UTF-8, or yet something else? I also recently discovered http://developer.apple.com/documentation/CoreFoundation/Reference/CFStringRe... (CFStringGetFileSystemRepresentation). It's perfectly usable when passing stuff to the posix api's, but when getting something back you still have to know what the used encoding was if you want to operate further on it. Mac OS X's posix filesystem API (open(2), stat(2), etc.) always expect path names to be UTF-8 encoded (the system will normalize them to be decomposed), and return path names which are UTF-8 encoded (decomposed). This email sent to site_archiver@lists.apple.com