• 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: NSString vs. encoding
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSString vs. encoding


  • Subject: Re: NSString vs. encoding
  • From: "Stephen J. Butler" <email@hidden>
  • Date: Wed, 16 Sep 2009 15:26:39 -0500

On Wed, Sep 16, 2009 at 3:13 PM, Johan Kool <email@hidden> wrote:
> I have been trying many combinations of encodings/decodings, but without the
> intended result. I do know what NSString wants, but that's not what I have.
> I have stringA as shown, and I have to somehow morph it into something
> usable. Basically I need NSString to interpret the characters a second time,
> but NSString seems to do all it can to keep it as is. Normally, that's
> indeed what I want, but not now...

I think you're going to have to write a special parser to handle this
encoding. Shouldn't be hard if you design your state machine properly.
_______________________________________________

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

References: 
 >Re: NSString vs. encoding (From: Greg Guerin <email@hidden>)
 >Re: NSString vs. encoding (From: Johan Kool <email@hidden>)

  • Prev by Date: Re: NSString vs. encoding
  • Next by Date: Re: What replaces the (now deprecated) NSObjCValueType?
  • Previous by thread: Re: NSString vs. encoding
  • Next by thread: Re: NSString vs. encoding
  • Index(es):
    • Date
    • Thread