Path: utzoo!utgpu!cs.utexas.edu!samsung!munnari.oz.au!brolga!uqcspe!batserver.cs.uq.oz.au!rhys From: rhys@batserver.cs.uq.oz.au (Rhys Weatherley) Newsgroups: alt.sources.d Subject: Re: A readable, robust encoding for source postings Message-ID: <6540@uqcspe.cs.uq.oz.au> Date: 31 Dec 90 12:00:47 GMT References: <4410@network.ucsd.edu> <1990Dec29.114801.5895@Daisy.EE.UND.AC.ZA> <1990Dec30.170302.21665@druid.uucp> Sender: news@uqcspe.cs.uq.oz.au Reply-To: rhys@batserver.cs.uq.oz.au Lines: 45 In <1990Dec30.170302.21665@druid.uucp> darcy@druid.uucp (D'Arcy J.M. Cain) writes: >In article <1990Dec29.114801.5895@Daisy.EE.UND.AC.ZA> Alan P. Barrett writes: >> [...] >>I think that the correct way to fix this is to use an encoding that is >>both readable and robust. A version of shar that does stuff like >>encoding tabs as \t and wrapping lines in a reversible way would do it. > >I posted my genfiles program which I hoped would be a jumpimg off point for >such an effort. Has anyone looked at it and have suggestions to enhance >the protocols I suggested? I missed the original discussion, so I may be repeating things, but the central problem I think there will be in getting a new transmission standard off the ground is actually making it a standard :-). unshar, uuencode and the like are very widespread, and trying to shake their ground may be very hard. Maybe in the interim a cut-down "encoder" is needed that can be wrapped-up in a shar archive, and will be unpacked, compiled and run to unpack the rest. e.g. the shar archive could look something like this: ... head information ... sed ... >/tmp/decode.c <file <