On Apr 6, 2015, at 9:57 AM, Charles Srstka <cocoa...@charlessoft.com> wrote: > > The problem, then, is likely the fact that NSCharacterSet considers a > “character” simply as a UTF-16 code point, rather than a true Unicode > character as Swift does.
That should not matter. UTF-16 is a variable length encoding. It is guaranteed to support all 1,112,064 possible Unicode characters. In order to do that it MUST be variable length, either 2-octets or 4-octets. This appears to be a bug in the Objective-C handling of UTF-16.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
