Re: BinSCII v2.0 ??????

[jmk3@crux3.cit.cornell.edu (Jay Krell)]

>If you did a little bit of algebra you'd see that he's doing about as good as
>13 bytes in 16.  4 bytes into 5 characters times 3 gives 12 bytes into 15
 
I did and I know.
 
>However, the problem with using the entire Apple II
>keyboard is that all of those characters may not be transmitted by certain
 
Ignorance strikes me here. I've heard that not all characters work
on every computer (I just heard of something called MIME as an
alternative to UUEncode and BinHex 'cause they use characters not
universally compatible; BinSCII probably does too.), but I've never
seen a definitely "These characters don't work on these computers, which
are used in so many places."
 
Anyone know which characters don't work on what?
 
Could the line length be arbitrary? though a non-multipe of 16 complicates
the code. "Odd" bytes in multiples of 4 could be encoded 4 in 5, though
that is more complicated than just doing all odd bytes in 1 in 2.
 

--
  --Jay, jay.krell@cornell.edu