• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSUnicodeStringEncoding
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSUnicodeStringEncoding

  • Subject: Re: NSUnicodeStringEncoding
  • From: Todd Heberlein <email@hidden>
  • Date: Sun, 13 Feb 2011 15:17:11 -0800
On Feb 11, 2011, at 11:10 AM, Kyle Sluder wrote:

> NSUnicodeStringEncoding is an alias for NSUTF16StringEncoding. You're
> best off getting UTF16 from your C++ string and explicitly using the
> NSUTF16StringEncoding constant when creating your NSString. Since
> UTF16 is the canonical representation of strings, this will result in
> the fewest conversions, and using the explicit UTF16 constant rather
> than the equivalent NSUnicodeStringEncoding will make your code
> clearer.
>
> --Kyle Sluder

Thanks!

[[NSString alloc] initWithBytes:byte_stream length:len encoding:NSUTF16LittleEndianStringEncoding]

worked for me.

Todd

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden
  • Follow-Ups:
    • Re: NSUnicodeStringEncoding
      • From: Kyle Sluder <email@hidden>
References: 
 >NSUnicodeStringEncoding (From: Todd Heberlein <email@hidden>)
 >Re: NSUnicodeStringEncoding (From: Kyle Sluder <email@hidden>)

  • Prev by Date: Re: Canceling NSInvocationOperation
  • Next by Date: Re: NSUnicodeStringEncoding
  • Previous by thread: Re: NSUnicodeStringEncoding
  • Next by thread: Re: NSUnicodeStringEncoding
  • Index(es):
    • Date
    • Thread