Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site cuae2.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!mgnetp!hw3b!wnuxb!cuae2!heiby
From: heiby@cuae2.UUCP (Heiby)
Newsgroups: net.micro.att
Subject: Re: 3b2 has no uuencode/uudecode??
Message-ID: <267@cuae2.UUCP>
Date: Mon, 27-May-85 12:52:48 EDT
Article-I.D.: cuae2.267
Posted: Mon May 27 12:52:48 1985
Date-Received: Thu, 30-May-85 20:17:06 EDT
References: <198@uwvax.UUCP> <1072@cp1.UUCP> <200@uwvax.UUCP>
Reply-To: heiby@cuae2.UUCP (Heiby)
Distribution: net
Organization: AT&T-IS, /app/eng, Lisle, IL
Lines: 18

In article <200@uwvax.UUCP> david@uwvax.UUCP (David Parter) writes:
>The purpose of uuencode/uudecode is to encode/decode binary files
>for transmission via (uucp) mail.  

Sounds like a KLUDGE to me.  If you want to transmit files, uucp works
fine, even on binary files.  I do it all the time.  Now, if you want to
pretend that these binary files are actually ASCII Text Mail, then you
do have a problem.  It shouldn't be to hard to read your binary and
translate each 8-bit char into two Hexadecimal digits, with about 80
characters of output per output line (40 input characters).  Reading
it back in would (of course) ignore the newlines.  If you don't have
a C compiler available to you, then you have more problems.

The real solution is to use uucp file transfer in the first place and
not pretend that binary files are just text.
-- 
Ron Heiby	heiby@cuae2.UUCP	(via wnuxa or wnuxb)
AT&T-IS, /app/eng, Lisle, IL	(312) 810-6109