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
elsewhere
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:
<http://savannah.gnu.org/bugs/?34486>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep
