Re: POSIX paths and UTF-8 on Mac OS X...
Re: POSIX paths and UTF-8 on Mac OS X...
- Subject: Re: POSIX paths and UTF-8 on Mac OS X...
- From: Chris Ridd <email@hidden>
- Date: Wed, 23 Nov 2005 16:47:07 +0000
- Thread-topic: POSIX paths and UTF-8 on Mac OS X...
On 23/11/05 4:37, Shawn Erickson <email@hidden> wrote:
> 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.
It is a bit Carbon-y, but there's some useful info in TN 2078:
<http://developer.apple.com/technotes/tn2002/tn2078.html>
Cheers,
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden