FROM : Shaun Wexler
DATE : Wed Jun 21 20:56:45 2006
On Jun 21, 2006, at 11:39 AM, Craig Altenburg wrote:
> The "Text Edit" sample applications defines strings with imbedded
> unicode characters:
>
> NSLocalizedString( @"Couldn\\U2019t open some of the specified
> files.", nil );
>
> This works -- the string displays with the "curly" apostrophe
> instead of the plain ASCII one.
>
> When I try the same thing in my program the "\U2019" is displayed.
>
> I looked at the compiler flags but don't see anything that they're
> doing that would account for the difference in behavior.
>
> Does anyone know what I need to do to get such strings recognized?
It only works in *C99 or C++, and you have one too many backslashes.
In Xcode, you'll find the build setting "C Language Dialect"...
--
Shaun Wexler
MacFOH
http://www.macfoh.com
DATE : Wed Jun 21 20:56:45 2006
On Jun 21, 2006, at 11:39 AM, Craig Altenburg wrote:
> The "Text Edit" sample applications defines strings with imbedded
> unicode characters:
>
> NSLocalizedString( @"Couldn\\U2019t open some of the specified
> files.", nil );
>
> This works -- the string displays with the "curly" apostrophe
> instead of the plain ASCII one.
>
> When I try the same thing in my program the "\U2019" is displayed.
>
> I looked at the compiler flags but don't see anything that they're
> doing that would account for the difference in behavior.
>
> Does anyone know what I need to do to get such strings recognized?
It only works in *C99 or C++, and you have one too many backslashes.
In Xcode, you'll find the build setting "C Language Dialect"...
--
Shaun Wexler
MacFOH
http://www.macfoh.com
| Related mails | Author | Date |
|---|---|---|
| Craig Altenburg | Jun 21, 20:39 | |
| Shaun Wexler | Jun 21, 20:56 | |
| Nick Zitzmann | Jun 21, 21:04 | |
| Clark Cox | Jun 22, 16:48 |






Cocoa mail archive

