site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=pWNk72RuNmB8P/1hPS6ld33fq3faNJ6PVSaD0oq5fhPu7LwgCoBFCQBTMAckzJD1siTUZV75IlQl0iM024TMesEXJAw75T6zZzR4beCoUzdRQS755CYF0rtiotRqnYbnUzYQ4Xi/zFQOTHCbD7IUU4ZRGfdNbsi2RoBYGnR4CA8= I am in the process of porting some software the runs on Windows to Mac OS X and I want to validate what I believe to be true on Mac OS X and also understand any special requirements that exist. I am fairly sure (and API docs support) that things like open and fopen accept UTF-8 (ASCII is a subset of UTF-8, so of course it accept traditional ASCII as well). Is this correct? I do see in Core Foundation code that in the new 10.4 method that returns the file system representation of of a CFString that UTF-8 is used but that it also attempts to do some specific type of string decomposition[1] (assume dealing with combining accents and the likes). So my question what exactly is expected and/or required in a UTF-8 string handed to something like fopen. Also can a BOM exist at the head of the UTF-8 string or must I assure that it doesn't exist. I tried to find a good document that calls things out fully but the best I could find was the UTF-8 is used. Thanks, -Shawn [1] Note yet tracked down the code to that function. _______________________________________________ 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... This email sent to site_archiver@lists.apple.com