From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.236.93.45 with SMTP id k33mr1791759yhf.19.1380321989861; Fri, 27 Sep 2013 15:46:29 -0700 (PDT) X-Received: by 10.49.64.72 with SMTP id m8mr101045qes.20.1380321989813; Fri, 27 Sep 2013 15:46:29 -0700 (PDT) Path: border1.nntp.dca3.giganews.com!border2.nntp.dca3.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!q9no104663qas.0!news-out.google.com!9ni501qaf.0!nntp.google.com!ek7no155703qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 27 Sep 2013 15:46:29 -0700 (PDT) In-Reply-To: <1eaeed6d-d047-4afc-b424-1713eada95fa@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=174.28.152.201; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 174.28.152.201 References: <1eaeed6d-d047-4afc-b424-1713eada95fa@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Information Request. From: Shark8 Injection-Date: Fri, 27 Sep 2013 22:46:29 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Original-Bytes: 3302 Xref: number.nntp.dca.giganews.com comp.lang.ada:183498 Date: 2013-09-27T15:46:29-07:00 List-Id: On Friday, September 27, 2013 2:08:02 PM UTC-6, Austin Obyrne wrote: >=20 > In my crypto scheme I'm planning on every message being prepared as a sri= ng of hex. I'm arguing that this is now a string of plaintext that can be = encrypted by any ASCII based encryption program (albeit hexadecimal digits = I plan to treat them as alphanumeric characters in ASCII)- it will decrypyt= exactly right I can assure everybody. >=20 > Alternatively I might read in the hexadecimal integer (180B say), convert= it decimal and use that as the operand in the computaton of my vector ciph= ertext. The benefit of doing this is that the ciphertext expansion is kept = to a minimum. >=20 > Both of these methods require the natural language plaintext to be submit= ted as a string of hex. That of course requires an interpreter on site. Er, it sounds to me as if you don't really know what you're talking about. = In general, there are two items in play dealing with text: the encoding, an= d the character-set. Unicode is a character-set [kinda], encoding for Unico= de can be 8-bit/variable-length, 16-bit/variable-length, 32-bit/fixed-lengt= h. In any case, the difference between the two is this: one maps some bit-s= equence to a value (this is the encoding), the other maps a value to a glyp= h (this is the character-set). Example: Value $4C =3D> '<' EBDIC Value $4C =3D> 'L' ASCII/Unicode Hex $e2b4a5 =3D> Value $2D25 (via 8-bit encoding) =3D> GEORGIAN SMALL LETTE= R HOE [unicode] Hex $00002d25 =3D> Value $2D25 (via 32-bit encoding) =3D> GEORGIAN SMALL LE= TTER HOE [unicode] So there are [at least] two different 'mappings' in place when you're talki= ng about text. (Three if you want to talk about typing, as there's somethin= g called keyboard scan-codes involved.)