[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #34486] gnustep has a problem with non-ascii string constants

From: julian
Subject: [bug #34486] gnustep has a problem with non-ascii string constants
Date: Wed, 05 Oct 2011 20:08:55 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.50 (KHTML, like Gecko) Version/5.1 Safari/534.50

Follow-up Comment #2, bug #34486 (project gnustep):

>historically non-ascii data in ObjC string constants has been disallowed

yes, historically, but this has been changed with Mac OS X 10.5 and i think
GNUstep should follow here. source files are encouraged to be UTF-8 and objc
string constants with special chars work now - though i couldn't find an
official apple document encouraging it. but the fact that they changed things
to make it work and  Xcode also doesn't warn on this even with all warnings
turned on - suggests its here to stay.

> discouraged all uses of anything which implies a default C string encoding

yes but i think C string encoding is a completely different issue. 

anyway i think this shouldn't be that high priority.

whats more disturbing is that even the workaround, manually specifying the
unicode escape sequences doesn't work. e.g.

[mybutton setTitle:@"Her name is Mu00E4dchen"]; // รค

how is this done in gnustep?


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]