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.32.74 with SMTP id n50mr1571898yha.13.1380314067692; Fri, 27 Sep 2013 13:34:27 -0700 (PDT) X-Received: by 10.50.16.111 with SMTP id f15mr169855igd.2.1380314067651; Fri, 27 Sep 2013 13:34:27 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!ek7no143709qab.0!news-out.google.com!9ni482qaf.0!nntp.google.com!q9no92191qas.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 27 Sep 2013 13:34:27 -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=193.59.74.178; posting-account=nuF4hQoAAADjc2KKS1rOkzxWWEmaDrvx NNTP-Posting-Host: 193.59.74.178 References: <1eaeed6d-d047-4afc-b424-1713eada95fa@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <6c2f0e98-44f9-4a67-b281-11943b5d258f@googlegroups.com> Subject: Re: Information Request. From: darkestkhan Injection-Date: Fri, 27 Sep 2013 20:34:27 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:17317 Date: 2013-09-27T13:34:27-07:00 List-Id: On Friday, September 27, 2013 8:08:02 PM UTC, Austin Obyrne wrote: > On Friday, September 27, 2013 7:33:14 PM UTC+1, Shark8 wrote: >=20 > > > My question is how is the interface with CJK provided =E2=80=93 there= must be somebody some where who converts the CJK into Unicode hexadecimal = code points for understanding by the keyboard person other wise she cannot = handle it. Usually via an IME (Input Method Editor [IIRC]), or a keyboard f= or the language [or setting your keyboard to that language, Windows allows = that (though the labeling on the board won't match)] -- If you're using Win= dows 7, there should be a "Regions and Languages" item in the Control Panel= : open it - then go to the "Keyboards and Languages" tab, - click the "Chan= ge Keyboard" button, another box titled "Text services and Input Languages"= [containing three tabs] should appear: - Click on the "General" tab, if no= t already there, - Click on Add to add an new keyboard (or language) And th= at's that. (Unless I misunderstand your question altogether.) >=20 >=20 >=20 > Lets say her name is Alice - the keyboard operator. >=20 >=20 >=20 > Alice now has a CJK keyboard on screen (I think) that she uses to mouse-= click in message characters in CJK (I don't envy her task). >=20 >=20 >=20 > I can see this working now but it seems a pretty inefficient way of doing= it - it must be very, very slow. >=20 >=20 >=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 >=20 >=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 >=20 >=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. >=20 >=20 >=20 > This is what has been bothering me - what does happen in practice??=20 >=20 >=20 >=20 > It doesn't sound to me as if Unicode is getting much use after all that u= p front in recent years. >=20 Unicode is used very commonly all around the world - main reason is that it= is interoperable between all (spoken) languages and systems (as long as th= ey support Unicode) You know what... =C5=9Bwiat jest wi=C4=99kszy ni=C5=BC CJK i angielski (wo= rld is bigger than CJK and english, written in Polish) - many European lang= uages are using additional letters, add to this cyrylic and some other alph= abets and then you will see how nice Unicode is. Just for your information = - before unicode we had several encoding methods for each language, making = things very complex. Now it is very simple - just handling Unicode (not tri= vial but at least we can assume something about input). As for inputting CJ= K - my best advise would be to try inputting some Japanese/Chinese. You wil= l see how it works (hint: romanization). There is no "big keyboard on the s= creen".