Re: NSStringEncoding troubles
Re: NSStringEncoding troubles
- Subject: Re: NSStringEncoding troubles
- From: Aki Inoue <email@hidden>
- Date: Sun, 14 Jul 2002 00:33:36 -0700
Adrian,
The NSString/CFString's encoding conversion machinary doesn't escape
non-printing bytes.
I assume you're using NSLog or something similar to experiment the
conversion result. Those functions just gives you back escaped
representation for display, but the actual data is preserved.
Aki
On 2002.7.13, at 03:21 PM, Adrian Rutledge wrote:
I'm writing an IRC app at the moment, and while [[NSString alloc]
initWithData:bleh encoding:NSSomeStringEncoding] works, it escapes
non-printing values such as ASCII 02. IRC uses several of the low
non-printing ASCII values for control codes, bold, underlines, CTCP,
color, etc. I want to stick with using the Cocoa provided encoding
and decoding stuff, that will save me a good deal of work when I,
eventually, add support for the Japanese encodings. (Should make it
nearly free, right? I'll have to research that some, later.) In any
case, is there any hidden argument I can give NSString or the NSData
instance to make it preserve non-printing characters exactly as they
are.
(Note, I thought about merely searching for the escaped sequences,
\002 and such, but that runs afoul of someone innocently or
not-so-innocently typing such a sequence and sending it, being able to
trick my client and make it react in a way I consider wrong.)
-Adrian
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.