FROM : Aki Inoue
DATE : Mon Apr 21 18:54:25 2008
>> (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 $(D+P(B 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
DATE : Mon Apr 21 18:54:25 2008
>> (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 $(D+P(B 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
| Related mails | Author | Date |
|---|---|---|
| Ewan Delanoy | Apr 21, 15:35 | |
| glenn andreas | Apr 21, 15:38 | |
| Jens Alfke | Apr 21, 16:48 | |
| Ewan Delanoy | Apr 21, 16:58 | |
| Ewan Delanoy | Apr 21, 17:04 | |
| Jean-Daniel Dupas | Apr 21, 17:35 | |
| Aki Inoue | Apr 21, 18:54 | |
| Jean-Daniel Dupas | Apr 21, 19:05 |






Cocoa mail archive

