Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!uwm.edu!bionet!agate!eos!amelia!roelofs
From: roelofs@amelia.nas.nasa.gov (Ender Wiggin)
Newsgroups: comp.os.os2
Subject: Re: encoding conventions--- please post nonstandard encoders
Message-ID: <6503@amelia.nas.nasa.gov>
Date: 4 Jun 90 08:04:38 GMT
Reply-To: roelofs@amelia.nas.nasa.gov (Ender Wiggin)
Followup-To: comp.os.os2
Organization: University of Chicago
Lines: 24

tom@mims-iris.waterloo.edu (Tom Haapanen) writes:

>As the moderator, I suppose I'm obliged to post a reply...
>
>Christian Motz <root@dialog.stgt.sub.org> writes:
>>                       Please create shell  archives  using  the
>> "shar"-utility from the split uuencoded files.  The big advantage is
>> that shar will also automatically extract the files as they were,
>> without the need for loading the file in an editor, removing leading
>> and trailing garbage like headers, signatures and so forth.

  [stuff deleted]

>The posting software used in comp.binaries.os2 is courtesy of Bill
>Davidsen and is the exact same thing used in comp.binaries.ibm.pc.
>
>Comments from anyone else?

Insofar as there is a standard "combine" script (at least on Unix boxes)
which handles the "leading and trailing garbage" quite adequately (without
the need for an explicit edit session), I for one see no particular reason
to change.  The only files *I* ever have to edit and clean up are shar 
files...(of course, there's probably an "unshar" program or something 
similar around here, but, well, er, I've never bothered to find out...).