Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!paperboy!meissner From: meissner@osf.org (Michael Meissner) Newsgroups: comp.lang.c Subject: Re: mailing binary files Message-ID: Date: 21 Feb 91 03:25:10 GMT References: <1025@tfsg.UUCP> <16968@crdgw1.crd.ge.com> <1991Feb20.224539.23290@Neon.Stanford.EDU> Sender: news@OSF.ORG Organization: Open Software Foundation Lines: 19 In-reply-to: espie@flamingo.Stanford.EDU's message of 20 Feb 91 22:45:39 GMT In article <1991Feb20.224539.23290@Neon.Stanford.EDU> espie@flamingo.Stanford.EDU (Marc Espie) writes: | So what's wrong with uuencode/uudecode ? The original uuencode/uudecode (ie, the one your UNIX vendor typically provides) does not work too well if sent through a PR1ME system, which strips trailing blanks from a line. I've also heard some of the characters used don't arrive intact if passed through an ASCII -> EBCDIC -> translation system, but I may be misremembering it.... Also, uuencode transmits more characters than atob/btoa (which come with the B news release), but those suffer from not being as universal as uuencode/uudecode. -- Michael Meissner email: meissner@osf.org phone: 617-621-8861 Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142 Considering the flames and intolerance, shouldn't USENET be spelled ABUSENET?