Re: Does NSString's "- initWithContentsOfURL:usedEncoding:error:" use the tightest encoding possible?
Re: Does NSString's "- initWithContentsOfURL:usedEncoding:error:" use the tightest encoding possible?
- Subject: Re: Does NSString's "- initWithContentsOfURL:usedEncoding:error:" use the tightest encoding possible?
- From: Jens Alfke <email@hidden>
- Date: Sat, 16 Apr 2016 23:19:56 -0700
> On Apr 16, 2016, at 7:35 PM, Daryle Walker <email@hidden> wrote:
>
> If the given method is used to read in a pure ASCII file, will the encoding be set to ASCII? Or could the method return a superset encoding (like Latin-1, MacRoman, or UTF-8)?
I don’t know; you could try it out, of course, but it sounds like the sort of undefined behavior you shouldn’t rely on.
If you’re trying to determine if the string is pure ASCII, you can use -rangeOfCharactersInSet: to look for anything above 127.
—Jens
_______________________________________________
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