Path: utzoo!attcan!uunet!cs.utexas.edu!usc!skat.usc.edu!acliu
From: acliu@skat.usc.edu (Alex C. Liu)
Newsgroups: comp.sys.cbm
Subject: Re: PetAscii to Ascii
Message-ID: <21347@usc.edu>
Date: 21 Nov 89 23:21:55 GMT
References: <1989Nov21.095017.21329@oswego.Oswego.EDU>
Sender: news@usc.edu
Reply-To: acliu@skat.usc.edu (Alex C. Liu)
Distribution: na
Organization: Maze Inc.
Lines: 22

In article <1989Nov21.095017.21329@oswego.Oswego.EDU> stjohn@oswego.oswego.edu.UUCP (Dave St. John) writes:
[ Few deleted lines ]
>in writing my own terminal program. The problem I have is I can't get the
>conversion to true Ascii right. I have the keyboard in lower case and map
>the lower case letters to their Ascii equivalent and when I send out across
>the modem I send the mapping. This works fine if I run the program without
>being connected to the Unix system. Once I am connected I get some of the
>characters no longer type in lower case and some only type in lower case.

What happens is that the Pet Ascii code has 2 sets of uper case
letters.  One is 128+CHR and the other is 32+CHR.  I found that the
best method to deal with conversion is trough a translation table (It
is simpler if you want to customize your keyboard).  The best way to
learn this is by looking at other program sources.  I wrote a C
program that does this conversion, that you can download from my
server (What a cheap comercial) in the power-c volume, as "conv.arc".
I think that would clear things up better.

---
Alex C. Liu 
acliu%skat@usc.edu	acliu@skat.usc.edu
(Simple .signature, $CHEAP$)