Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!sri-spam!mordor!lll-tis!ptsfa!hoptoad!academ!killer!tad
From: tad@killer.UUCP (Tad Marko)
Newsgroups: comp.unix.wizards,comp.misc,comp.sources.d
Subject: UUDECODE and trailing spaces
Message-ID: <924@killer.UUCP>
Date: Fri, 22-May-87 09:52:02 EDT
Article-I.D.: killer.924
Posted: Fri May 22 09:52:02 1987
Date-Received: Sun, 24-May-87 08:54:25 EDT
Organization: The Home for the Terminally Apathetic.
Lines: 17
Keywords: a possible solution
Xref: mnetor comp.unix.wizards:2448 comp.misc:576 comp.sources.d:711

I've been noticing a lot of people complaining lately about uuencoded
files being screwed up by having trailing spaces removed.  In a future
version of uuencode, why can't the spaces either *always* be guaranteed
to be there (ie. by being sealed in by a character that always marks
the end of lines) or make a uudecode that doesn't need them (ie. it
figures that since this line is short, it needs to be padded)?  I can't
imagine that either of these solutions would be very difficult except the
former might cause some compatiblity problems until everyone got the new
uudecode.

Tad
--
Tad Marko
..!ihnp4!killer!tad		||	..!ihnp4!alamo!infoswx!ntvax!tad
UNIX Connection BBS AT&T 3B2		North Texas State U. VAX 11/780

"Hi there!" -- Peter Gabriel in "Big Time"