Re: Conflicting encodings issue in a Cocoa app
Re: Conflicting encodings issue in a Cocoa app
- Subject: Re: Conflicting encodings issue in a Cocoa app
- From: Jean-Daniel Dupas <email@hidden>
- Date: Mon, 21 Apr 2008 19:05:01 +0200
Le 21 avr. 08 à 18:54, Aki Inoue a écrit :
(By the way, in 10.5, GCC now allows you to use non-ascii
characters in string literals right in your source code. So
there's no need to construct a string with an ñ in it
programmatically, as long as you're building with Xcode 3.0.)
What will be the output encoding in this case ? GCC generate utf-8
or it uses the source file encoding ?
Regardless of GCC binary C string encoding settings, the content of
constant CF/NSStrings are stored in UTF-16 in this case.
So, as long as your file encoding matches the GCC's file encoding
setting (see -finput-charset) which is default to UTF-8, it just
works.
Aki
Thank you.
I didn't realize that "string literals" means CF/NSStrings and not
standard C strings.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden