Re: Why would -[NSString dataUsingEncoding:allowLossyConversion:] throw exception?
Re: Why would -[NSString dataUsingEncoding:allowLossyConversion:] throw exception?
- Subject: Re: Why would -[NSString dataUsingEncoding:allowLossyConversion:] throw exception?
- From: Sherm Pendley <email@hidden>
- Date: Mon, 8 Jan 2007 18:04:57 -0500
On Jan 8, 2007, at 5:10 PM, Dan Wood wrote:
I'm trying to downsample a string to pure ASCII using the -
[NSString dataUsingEncoding:allowLossyConversion:] like this:
NSData *asciiData = [theString
dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES];
However, in some circumstances I get an exception thrown:
*** -[NSCFString dataUsingEncoding:allowLossyConversion:]: didn't
convert all characters
For instance, when I pass in the string "Det er gratis…" (the last
character is U+2026) it happens.
I'm not finding any documentation that it might throw an exception.
No, it's not documented that I can find. I'd file a docs bug.
Isn't the point of passing in YES so that you can still get
something back even if not all characters are converted?
Yes, but I can see why it might be useful to be notified when
something got lost in translation, and this method predates the
NSError class that's in vogue these days. You could catch and handle
the exception easily enough, or avoid it entirely with -
canBeConvertedToEncoding:.
sherm--
Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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