yes, it is for a small hex reader.
I need to read some old c64 file (.prg) then
visualize the hex and the ascii
so when I translate this:
01 08 0B 08 01 00 9E 32 30 36 31 00 00 00 A9 93
20 D2 FF A9 08 85 FC 8D 6B 10 A9 38 8D DC 17 A9
30 8D DB 17 A9 37 85 01 A9 13
I get this:
î2061
Maybe I'm missing something from your example, previous postings, and my ISP's
web mail client, but it appears your desired output doesn't seem to match in
character count to your original text. Nevertheless, if all you want is to
turn low-ASCII (values less than 0x20) and high-ASCII (values
this is a cool idea.
mapping into an array all the chars I need and run the parse..
quite cool.tnx!
I need to call the parse only one time after loaded the .prg C64 file.
Maybe I'm missing something from your example, previous postings,
and my ISP's web mail client, but it appears your
hello guys,
is a way to convert an unicode string into a simple a-z0-9 string
and replace the other wierd chars into a . (full stop)?
im doing a small hex reader, so maybe this could help you.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
The simplest way I've accomplished this is:
[[NSString alloc] initWithCString:(const char *)nullTerminatedCString
encoding:(NSStringEncoding)encoding];
Where encoding is :NSUTF8StringEncoding
You will then have to replace the unknown char with a . with the
NSString method:
Just to point this out, the sequence of ASCII may not be useful at all
if the file is say Unicode. The actual bytes making up each char could
be ASCII values themselves.
Sent from my iPhone
On Aug 28, 2008, at 1:53 PM, Martin Stoufer [EMAIL PROTECTED] wrote:
The simplest way I've
On 28 Aug 08, at 12:08, Ricky Sharp wrote:
Just to point this out, the sequence of ASCII may not be useful at
all if the file is say Unicode. The actual bytes making up each char
could be ASCII values themselves.
Unicode is a character set, not an encoding. I'm not sure about UTF-16
or
On Aug 28, 2008, at 3:40 PM, Andrew Farmer wrote:
On 28 Aug 08, at 12:08, Ricky Sharp wrote:
Just to point this out, the sequence of ASCII may not be useful at
all if the file is say Unicode. The actual bytes making up each
char could be ASCII values themselves.
Unicode is a character
You can use CFStringTransform to process Unicode in several ways that
might be useful for what you're doing. Or you can just go through it
character by character. To see what CFStringTransform can do, see:
http://icu-project.org/userguide/Transform.html
I should point out that you can only
On Aug 28, 2008, at 3:48 PM, I. Savant wrote:
On Aug 28, 2008, at 6:36 PM, Deborah Goldsmith wrote:
I should point out that you can only write English with a-z, so I
don't know if I'd consider the other characters weird. Not to
mention characters like ¥, ©, and so on.
Here's an
10 matches
Mail list logo
