I'm pretty sure that's what NSLiteralSearch does. In practice for me, I found the difference is that composed/decomposed character sequences are scene as being the same when using compare with no options, but that there's a difference when using NSLiteralSearch (and by extension, -isEqualToString:)
On 16 Aug 2011, at 17:44, Jens Alfke wrote: > Anyone know what the exact behavior of NSLiteralSearch is when calling > -[NSString compare:options:]? > > I need to sort an array of NSStrings, with the ordering based on a raw > comparison of UTF-16 character values*. That is, sorting the strings as > though they were just arrays of UInt16, instead of using any kind of Unicode > smarts or locale-specific settings. It sounds as though NSLiteralSearch does > that, but the docs don’t actually spell it out. > > —Jens > > * Why? To produce canonicalized JSON. See > <http://wiki.apache.org/couchdb/SignedDocuments>_______________________________________________ > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/cocoadev%40mikeabdullah.net > > This email sent to cocoa...@mikeabdullah.net _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
