Follow-up Comment #1, bug #34486 (project gnustep):
I think this is probably an application bug since historically non-ascii data
in ObjC string constants has been disallowed (ie strings documented as having
to be ascii and behavior for non-ascii documented as unsupported/undefined).
Apple have also active discouraged all uses of anything which implies a
default C string encoding elsewhere, and have afaik deprecated all such
methods ... so they seem serious about being well behaved and requiring you to
specify the encoding of all C strings generally.
However ...
1. you may know of some recent documentation defining a policy change and
specifying how non-ascii data is to be handled in future or
2. it might be worth reverse engineering the latest OSX behavior and
implementing that even if apple don't want developers to depend on it.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?34486>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-gnustep
