HDTenEightyP/NetNews huggingface dataset:
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: X.400 and multimedia mail
Date: Sun, 13 Dec 1992 22:11:21 GMT
Organization: U of Toronto Zoology

In article <1gfg5uINN5ej@calvin.NYU.EDU> roy@mchip00.med.nyu.edu (Roy Smith) writes:
>	What ever happened to btoa?  It came out a bunch of years ago, but
>never seemed to catch on.  As I remember, it was touted as a replacement for
>uuencode with the advantage that it only incurred a 5/4ths expansion instead
>of 4/3rds.  Was there some reason why MIME didn't use btoa?

The MIME people worked hard to find an encoding that would survive *anywhere*
in the known RFC822-mail universe.  This is a lot harder than it looks, when
you start thinking ugly thoughts like "Bitnet".  Many of the non-alphanumeric
ASCII characters are vulnerable to mangling in gateways.  You can't beat six
bits/character (i.e. 4/3 expansion) by much without using vulnerable
characters.
-- 
"God willing... we shall return."       | Henry Spencer @ U of Toronto Zoology
       -Gene Cernan, the Moon, Dec 1972 |  henry@zoo.toronto.edu  utzoo!henry
Newsgroups: comp.mail.mime
From: olevi@daimi.aau.dk (Ole Villumsen)
Subject: Re: Frequently asked questions about MIME
Organization: DAIMI: Computer Science Department, Aarhus University, Denmark
Date: Thu, 17 Dec 92 10:46:23 GMT

hta@boheme.er.sintef.no (Harald Tveit Alvestrand) writes:

...
>I don't know enough about NeXT to know whether it is an UNIX or a strange
>beast, though I suspect the latter....

The NeXT is sorta both - pure Unix, but with a lotta fancy stuff on top of it.
As far as I've understood.

Ole

 Ole V. Villumsen              
 Computer Science Department, Aarhus University, Denmark
 ovillumsen@daimi.aau.dk

"Your quote here" (Bjarne Stroustrup)
Newsgroups: comp.mail.mime
From: hta@boheme.er.sintef.no (Harald Tveit Alvestrand)
Subject: Re: Frequently asked questions about MIME
Reply-To: harald.alvestrand@delab.sintef.no
Organization: SINTEF DELAB, Norway
Date: Wed, 16 Dec 92 13:49:14 GMT

Ed,
BEAUTIFUL!
But of course it needs some work.

One note:

5. Free MIME software packages.

5.1 free MIME FOR SunOS 4.1.x:
5.2 free MIME FOR BSD
5.3 free MIME for SYSVR4:
5.4 FREE MIME FOR MSDOS:
5.5 free MIME for AmigaOS:
5.6 free MIME for NeXT:
5.7 free MIME for Macintosh:


I do not think dividing between SunOS, BSD and SysVR4 makes sense.
Where would MIXmh fit?

Possibly it would be better to say something like:

5.x Free MIME for Unix/X           (mixmh)
5.x Free MIME for Unix/Terminals   (mhn, pine)
5.x Free MIME for PC/Windows
5.x Free MIME for PC/character based (pine again, I THINK)
5.x Free MIME for AmigaOS
5.x Free MIME for Macintosh

I don't know enough about NeXT to know whether it is an UNIX or a strange
beast, though I suspect the latter....

-- 
                   Harald Tveit Alvestrand
Harald.Alvestrand@delab.sintef.no
C=no;PRMD=uninett;O=sintef;OU=delab;S=alvestrand;G=harald
+47 7 59 70 94
Newsgroups: comp.mail.mime,comp.mail.multimedia
From: pte900@jatz.aarnet.edu.au (Peter Elford)
Newsgroups: comp.mail.mime
Subject: Re: MIME for VMS?
Date: 19 Dec 1992 10:21:54 GMT
Organization: Australian National University
NNTP-Posting-Host: 139.130.204.4
X-Newsreader: TIN [version 1.1 PL8]

Per Steinar Iversen (iversen@dsfys1.fi.uib.no) wrote:
: Is there any public domain package that does MIME for VMS MAIL?

I believe that PMDF has MIME support. Although not free, it is available
at relatively low cost from innosoft.com.

--
Peter Elford,                             e-mail: P.Elford@aarnet.edu.au
Network Co-ordinator                      phone: +61 6 249 3542
Australian Academic Research Network      fax:   +61 6 249 1369
c/o, Computer Services Centre             pager: +61 6 245 3035
Australian National University            post: GPO Box 1142     
Canberra, AUSTRALIA                             Canberra ACT 2601
Newsgroups: comp.mail.mime
From: davecb@nexus.yorku.ca (David Collier-Brown)
Subject: Re: X.400 and multimedia mail
Organization: York University
Date: Sat, 12 Dec 1992 03:20:13 GMT



|In article <1galsqINNr88@gap.caltech.edu> jack@ccsf.caltech.edu (Jack Stewart) writes:
|>As I understand, the main reason for MIME to use base64 encoding (as
|>opposed to uuencode, 8bit transparent, XDR, or BER ) was that they
|>needed an encoded scheme that would remain uncorrupted accross all
|>platforms and architectures and existing mailers.  Apparently this is
|>a real problem with IBM VM/CMS machines.  base64 encoding was the only
|>thing that would survive these machines.  Hopefully these machines
|>will go away some day and then we can use a more reasonable encoding
|>mechanism.

ag129@cus.cam.ac.uk (Alasdair Grant) writes:
|Yes, but this is a minor problem compared to the presence of machines
|which use the 7-bit American ASCII code, where the top bit is a parity
|bit.

  Since no-one buys GCOS anymore, who cares? (half a (:-)).

  Seriously, though, there are very few machines still in existance which have
a byte size of 6 bits or less.  Given that common communications channels
are 8-bit, it is reasonable to expect that an 8-bit-clean smtp path and
an 8-bit-clean file system will allow the elimination of 7-bit ascii as 
soon as it's worth the vendors' while.  16-bit is the real problem.

--dave 
[ps: Honeywell, IBM 7070s and DEC-10s ran to 36-bit words, and tended
 to use 6-bit almost-ascii codes. Honeybuns actually could store
 strings of 7-bit characters, assuming you really, truly, wanted to.
 Sane honeybuns ran Multics, however, and used 9-bit bytes. --dave]
-- 
David Collier-Brown,  | davecb@CCS.YorkU.CA | lethe!dave
72 Abitibi Ave.,      | 
Willowdale, Ontario,  | York Postmaster and
CANADA. 416-223-8968  | occasional sendfail(8) consultant.
Newsgroups: comp.mail.mime
From: vances@xenitec.on.ca (Vance Shipley)
Subject: mush (was Re: Mailstrom and pcpine)
Organization: XeniTec Consulting, Kitchener, Ontario, CANADA
Date: Sat, 19 Dec 1992 00:11:58 GMT

I am under the impression that mush will support mime in the next
release.  What is my best bet at this point for SCO ODT v2.0
(SYSV R3.2v4 X11R4)?

-- 
Vance Shipley 
vances@xenitec.on.ca         vances@switchview.com         vances@ltg.uucp
Newsgroups: comp.mail.mime
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: X.400 and multimedia mail
Date: Sun, 13 Dec 1992 03:18:04 GMT
Organization: U of Toronto Zoology

In article <1galsqINNr88@gap.caltech.edu> jack@ccsf.caltech.edu (Jack Stewart) writes:
>As I understand, the main reason for MIME to use base64 encoding (as
>opposed to uuencode, 8bit transparent, XDR, or BER ) was that they
>needed an encoded scheme that would remain uncorrupted accross all
>platforms and architectures and existing mailers.  Apparently this is
>a real problem with IBM VM/CMS machines.  base64 encoding was the only
>thing that would survive these machines.  Hopefully these machines
>will go away some day and then we can use a more reasonable encoding
>mechanism.

What would be "more reasonable"?  I can well believe that CMS was the
worst case, but if you want to transmit arbitrary bits, there are lots
of other systems with limitations that make an encoding necessary.
(For example, most sendmail implementations croak on 8-bit characters
in headers, I'm told.)

Also, can you explain your list of "as opposed to" encodings?  It seems
to mix several different issues.  XDR and BER are ways of encoding higher-
level data structures as a bit stream, not ways of getting arbitrary bits
through limited channels.  8-bit transparent isn't an encoding, it's the
*absence* of an encoding.  And uuencode is essentially identical to
base64 except that it's not as good, due to some fundamental design
mistakes; in particular, it isn't any more compact.
-- 
"God willing... we shall return."       | Henry Spencer @ U of Toronto Zoology
       -Gene Cernan, the Moon, Dec 1972 |  henry@zoo.toronto.edu  utzoo!henry
From: lyndon@unbc.edu (Lyndon Nerenberg)
Newsgroups: comp.mail.mime
Subject: Re: X.400 and multimedia mail
Date: 14 Dec 92 20:15:30 GMT
Organization: University of Northern B.C.

ddj+@cs.cmu.edu (Doug DeJulio) writes:

> What about BAUDOT?

You've got to be kidding :-)  Seriously, is there an MTA out there that
actually runs on BAUDOT? (Hmm ... if you consider AMTOR BBS's as MTA's
then the answer is *yes* surprisingly enough!)

> How about the standard APL character set?

Convention was to map upper/lower case to underscored/non-underscored
letters. Which way the mapping went tended to be site-dependent.

--lyndon
Newsgroups: comp.mail.mime
From: bugs@atlantis.uucp (Dan Berry)
Subject: Re: Frequently asked questions about MIME
Organization: Atlantis Communications, Edmonton, AB, Canada
X-Newsreader: TIN [version 1.1 PL7]
Date: Fri, 18 Dec 1992 01:53:29 GMT

Harald Tveit Alvestrand (hta@boheme.er.sintef.no) wrote:
: I do not think dividing between SunOS, BSD and SysVR4 makes sense.
: Where would MIXmh fit?
: 
: Possibly it would be better to say something like:
: 
: 5.x Free MIME for Unix/X           (mixmh)
: 5.x Free MIME for Unix/Terminals   (mhn, pine)
: 5.x Free MIME for PC/Windows
: 5.x Free MIME for PC/character based (pine again, I THINK)
: 5.x Free MIME for AmigaOS
: 5.x Free MIME for Macintosh
: 
: I don't know enough about NeXT to know whether it is an UNIX or a strange
: beast, though I suspect the latter....

Aye, it is a strange beast in that it operates under the NeXTSTEP window
server, but it does use BSD-like Unix with a Mach kernel.

The sections should indicate the separate (non-)graphical environments,
according to your method.
	Hence: Unix/X, Unix/NeXTSTEP, Unix/Terminals, etc. etc...
-- 
Dan Berry			bugs%atlantis@kakwa.ucs.ualberta.ca
==============================> bugs@atlantis.uucp  =========================
"On a first date, watch how your date treats the waiter, the bartender,
	and so on.  That's how she'll be treating YOU after three months."
Newsgroups: comp.mail.mime
From: lwv26@cas.org (Larry W. Virden)
Subject: Re: MIME on NeXT
Followup-To: comp.mail.mime
Reply-To: lvirden@cas.org (Larry W. Virden)
Organization: Nedriv Software and Shoe Shiners, Uninc.
Date: Sat, 19 Dec 1992 11:11:00 GMT

It sure would be nice if someone would port something like this to X11...
-- 
Larry W. Virden                 UUCP: osu-cis!chemabs!lvirden
Same Mbox: BITNET: lvirden@cas  INET: lvirden@cas.org
Personal: 674 Falls Place,   Reynoldsburg, OH 43068-1614
From: tml@tik.vtt.fi (Tor Lillqvist)
Newsgroups: comp.mail.mime
Subject: Re: X.400 and multimedia mail
Date: 15 Dec 92 00:09:26
Organization: Technical Research Centre of Finland, Laboratory for Information
	Processing (VTT/TIK)
	<Bz9B07.8Bo.2@cs.cmu.edu> <369@unbc.edu>
NNTP-Posting-Host: tik.vtt.fi
In-reply-to: lyndon@unbc.edu's message of 14 Dec 92 20:15:30 GMT

In article <369@unbc.edu> lyndon@unbc.edu (Lyndon Nerenberg) writes:
> You've got to be kidding :-)  Seriously, is there an MTA out there that
> actually runs on BAUDOT?

Yes, certainly... Well, almost. I have seen examples of commercial
e-mail systems, presumably unable to speak to each other directly,
exchanging mail via telex...

Another case: telex is pretty widespread in the former SU (and in many
developing countries, I guess), and I think much commercial e-mail
traffic originating in X.400 or whatever gets relayed to such
destinations via telex by various gateways.  I don't now how
bi-directional these kinds of gateways are, though.

Isn't (radio) telex also widespread onboard merchant ships? Are there
connections to this "network" from e-mail systems?
--
Tor Lillqvist,
working, but not speaking, for the Technical Research Centre of Finland,
Laboratory for Information Processing (VTT/TIK).
Newsgroups: comp.mail.mime
From: jsweet@irvine.com (Jerry Sweet)
Subject: Re: Frequently asked questions about MIME 
             <1992Dec19.023707.26489@cbfsb.cb.att.com> 
Organization: Irvine Compiler Corp., Irvine, California, USA
Date: Sat, 19 Dec 1992 04:05:04 GMT
To: rprice@cbnewsg.cb.att.com (rodney.price)

Starting over a year ago, Marshall Rose made no bones about wanting
someone to help to configure MH-MIME for the NeXT.  At that time,
someone at NeXT had managed to get some version of MH to compile under
NeXT/Mach 2.1, but wasn't widely publicizing the patches ...although
that person did pipe up at a BANG meeting a year or so ago when I
brought up the subject there.

MH was otherwise difficult to compile on the NeXT for someone with a
limited time budget.  MH 6.8 is out now; perhaps things are different
for compiling it on a NeXT, since MH 6.8 makes a few more concessions
to ANSI C compatibility.

Well, no one can accuse MH of having a beautiful graphical user
interface based tool for creating MIME messages, but it does support
MIME, no question about it.

With respect to NeXTmail, by way of contrast, here is an excerpt from
my contribution to the FAQ (the new version of which isn't out yet)
regarding other multi-media e-mail user agents:

> The ability to create e-mail messages with audio and other non-textual
> contents has been around for a while, but almost always as part of a
> vendor-specific ``solution.''  This means that you can't create a
> message on a NeXT system containing PostScript information and ``Lip
> Service'' (NeXT's audio e-mail tool) and easily handle the same
> message on an HP 9000/710, a Sun SPARCstation IPC, and a Silicon
> Graphics Iris.  That's a problem that MIME helps to solve.

It isn't much different from what you said.  The point, which you've
already noted, Rodney, is that a multi-media e-mail solution that
works only with NeXTs doesn't cut the mustard.
Newsgroups: comp.mail.mime
From: wilcoxt@cuug.ab.ca (Terrance Wilcox 229-3361)
Subject: Re: Frequently asked questions about MIME
Organization: Calgary UNIX User's Group
Date: Fri, 18 Dec 1992 14:43:38 GMT

In article <1992Dec16.134914.2910@ugle.unit.no> harald.alvestrand@delab.sintef.no writes:
>I do not think dividing between SunOS, BSD and SysVR4 makes sense.
>Where would MIXmh fit?
>
>Possibly it would be better to say something like:
>
>5.x Free MIME for Unix/X           (mixmh)
>5.x Free MIME for Unix/Terminals   (mhn, pine)
>5.x Free MIME for PC/Windows
>5.x Free MIME for PC/character based (pine again, I THINK)
>5.x Free MIME for AmigaOS
>5.x Free MIME for Macintosh
>
>I don't know enough about NeXT to know whether it is an UNIX or a strange
>beast, though I suspect the latter....

The NeXT is BSD, but the free mime package for the NeXT is neither Unix/X
nor Unix/Terminals. It's NeXTSTEP, so NeXT should be left in the list.

Terry Wilcox




Newsgroups: comp.mail.mime
From: iversen@dsfys1.fi.uib.no (Per Steinar Iversen)
Subject: MIME for VMS?
Reply-To: iversen@vsfys1.fi.uib.no
Organization: Department of Physics, University of Bergen, Norway
Date: Fri, 18 Dec 92 08:05:43 GMT



Is there any public domain package that does MIME for VMS MAIL?

(I have received occasional messages with the ISO8859-1 encoding, they are not
very nice to read unless decoded into 8bit format.)

-psi

+------------------------------------------------------------------------------+
! Per Steinar Iversen    ! Internet:     iversen@vsfys1.fi.uib.no              !
! Fysisk Institutt       ! BITnet:       iversen@cernvm.bitnet                 !
! Universitetet i Bergen ! HEPnet:       VSFYS::IVERSEN (VSFYS=21.341=21845)   !
! Allegaten 55           ! Phone:       +47 5212770                            !
! N-5007 Bergen          ! Fax:         +47 5318334                            !
! NORWAY                 !                                                     !
+------------------------------------------------------------------------------+
Newsgroups: comp.mail.mime
From: ecf_stbo@jhuvms.hcf.jhu.edu (You never forget your first gale)
Subject: Re: MIME for VMS?
News-Software: VAX/VMS VNEWS 1.41    
Organization: The Johns Hopkins University - HCF
Date: Fri, 18 Dec 1992 22:00:00 GMT

In article <1992Dec18.080543.6827@alf.uib.no>, iversen@vsfys1.fi.uib.no writes...
>Is there any public domain package that does MIME for VMS MAIL?

I don't know of any yet. PMDF isn't very expensive though.


Tom O'Toole - ecf_stbo@jhuvms.hcf.jhu.edu - JHUVMS system programmer 
Homewood Computing Facilities, Johns Hopkins University, Balto. Md. 21218 
>Here comes a jet ski.
>weuh weeuhh weeuhh weeuhh WEEUHH WEEUHH WEEUHH WEEUHH weeuhh weeuhh weeuhh weuh
From: pjones@mento.oit.unc.edu (Paul Jones)
Subject: Mailstrom and pcpine
Reply-To: pjones@mento.oit.unc.edu (Paul Jones)
Organization: UNC Office of Information Technology
Date: Fri, 18 Dec 1992 16:50:54 GMT

I keep hearing that Mailstrom will support MIME, but the version I just got  
from Washington doesn't. I've also been hearing a lot about pcpine (we love  
the unix pine), but again it's nowhere to be found. I know that I should  
probably wait until Ed V. get the MIME FAQ out, but I'm like to know something  
sooner if possible. Can anyone enlighten me?

Thanks.

--
==============================================
       Paul Jones
       Office FOR Information Technology
       University of North Carolina
       Chapel Hill, NC
       Paul_Jones@unc.edu
Newsgroups: comp.mail.mime
From: rprice@cbnewsg.cb.att.com (rodney.price)
Subject: Re: Frequently asked questions about MIME
Summary: please include NeXT
Organization: AT&T
Date: Sat, 19 Dec 1992 02:37:07 GMT

> : I do not think dividing between SunOS, BSD and SysVR4 makes sense.
> : Where would MIXmh fit?
> : 
> : Possibly it would be better to say something like:
> : 
> : 5.x Free MIME for Unix/X           (mixmh)
> : 5.x Free MIME for Unix/Terminals   (mhn, pine)
> : 5.x Free MIME for PC/Windows
> : 5.x Free MIME for PC/character based (pine again, I THINK)
> : 5.x Free MIME for AmigaOS
> : 5.x Free MIME for Macintosh
> : 
> : I don't know enough about NeXT to know whether it is an UNIX or a strange
> : beast, though I suspect the latter....
> 
> Aye, it is a strange beast in that it operates under the NeXTSTEP window
> server, but it does use BSD-like Unix with a Mach kernel.
> 
> The sections should indicate the separate (non-)graphical environments,
> according to your method.
> 	Hence: Unix/X, Unix/NeXTSTEP, Unix/Terminals, etc. etc...

I hope that you will include NeXT in the FAQ somewhere, preferably
as suggested here.  I have a NeXT; it has a very nice proprietary
graphical mail app that allows you to send RTF text, graphics, sound
files, whatever you like.  For instance, if you want to mail a file,
you drag the file's icon into the body of the letter, where it stays.
The person receiving the file drags the icon out of the mail and drops
it where he wants it, and he's done.  Graphics can be pasted in; if
you want to annotate your text with voice you click on the appropriate
button, talk, click again, and a pair of lips appears at the point your
cursor is at.  It's all very nice, seamless, transparent, but there's 
one big catch -- it only works with other NeXT machines.

A few months ago, there was discussion on one of the comp.sys.next
groups about writing some code to allow the NeXT Mail app to use
MIME format messages, but it went nowhere, as far as I know.  If
there is a free MIME for the NeXT I'd love to hear about it.  Even
if there isn't, it might be appropriate for someone knowledgable about
both NeXT and MIME to make some comments in the FAQ.

> Dan Berry			bugs%atlantis@kakwa.ucs.ualberta.ca
> ==============================> bugs@atlantis.uucp  =========================
> "On a first date, watch how your date treats the waiter, the bartender,
> 	and so on.  That's how she'll be treating YOU after three months."
   ^^^^^^^^^^^
   True -- very true.  Great sig.

Rod Price
rprice@physics.att.com
From: mrc@Ikkoku-Kan.Panda.COM (Mark Crispin)
Newsgroups: comp.mail.mime
Subject: MIME on NeXT
Date: 19 Dec 92 04:40:09 GMT
Article-I.D.: Ikkoku-K.MS-C.724740009.377401575.mrc
Organization: University of Washington
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0

My MailManager application on the NeXT has supported MIME (and IMAP, and
various mailbox formats) for quite some time.  It's on ftp.cac.washington.edu
in the mail/ directory.
Newsgroups: comp.mail.mime
From: ag129@cus.cam.ac.uk (Alasdair Grant)
Subject: Re: X.400 and multimedia mail
Organization: U of Cambridge, England
Date: Fri, 11 Dec 1992 20:19:47 GMT

In article <1galsqINNr88@gap.caltech.edu> jack@ccsf.caltech.edu (Jack Stewart) writes:
>As I understand, the main reason for MIME to use base64 encoding (as
>opposed to uuencode, 8bit transparent, XDR, or BER ) was that they
>needed an encoded scheme that would remain uncorrupted accross all
>platforms and architectures and existing mailers.  Apparently this is
>a real problem with IBM VM/CMS machines.  base64 encoding was the only
>thing that would survive these machines.  Hopefully these machines
>will go away some day and then we can use a more reasonable encoding
>mechanism.

Yes, but this is a minor problem compared to the presence of machines
which use the 7-bit American ASCII code, where the top bit is a parity
bit.  EBCDIC, as used by VM/CMS (and MVS and DOS), is an 8-bit code.
Neither uuencode nor base64 are 'reasonable', since they both 'waste'
bandwidth, but the reason they exist is fundamentally because ASCII
is a 7-bit code.

By the way, there are lots of other machines which have even _fewer_
printable characters than VM/CMS.
From: moore@cs.utk.edu (Keith Moore)
Newsgroups: comp.mail.mime
Subject: Re: X.400 and multimedia mail
Date: 14 Dec 1992 19:02:36 GMT
Organization: Univ. of Tenn. Computer Science, Knoxville
Distribution: world
Reply-To: moore@cs.utk.edu
NNTP-Posting-Host: wilma.cs.utk.edu

In article <Bz9B07.8Bo.2@cs.cmu.edu>, ddj+@cs.cmu.edu (Doug DeJulio) writes:
> In article <1gg2qjINN2df@chnews.intel.com> bhoughto@sedona.intel.com (Blair P. Houghton) writes:
> >RFC 1341 explicitly cites a desire to use only characters
> >which appear in all[*] extant literal standards.  The set
> >[A-Za-z0-9+/] (the brackets aren't included) appears just
> >about everywhere.
> [...]
> >[*] almost all? I don't remember any exceptions.
> 
> What about BAUDOT?
> How about the standard APL character set?
> Neither of these has lower case if my memory serves.

Perhaps a better way to express it is: "only characters that appear
in all of the worlds that currently exchange rfc822-like-mail". [*]
That includes not only ASCII but several of the ISO 646 variants and
several versions of EBCDIC.  And there are a few others besides.
The point is to be Installed-Base Friendly.

(Gee, if you want to exchange MIME mail using Baudot, you could
probably use quoted-printable and RFC 1342's "Q" encoding to do it.
I think all the necessary characters are there.)

--
Keith Moore / U.Tenn CS Dept / 107 Ayres Hall / Knoxville TN  37996-1301
Internet: moore@cs.utk.edu      BITNET: moore@utkvx
UNIX is your brain..............SYSV is your brain on drugs.
From: roy@mchip00.med.nyu.edu (Roy Smith)
Newsgroups: comp.mail.mime
Subject: Re: X.400 and multimedia mail
Date: 13 Dec 1992 14:09:02 GMT
Organization: New York University, School of Medicine
NNTP-Posting-Host: mchip00.med.nyu.edu

henry@zoo.toronto.edu (Henry Spencer) writes:
> And uuencode is essentially identical to base64 except that it's not as
> good, due to some fundamental design mistakes; in particular, it isn't any
> more compact.

	What ever happened to btoa?  It came out a bunch of years ago, but
never seemed to catch on.  As I remember, it was touted as a replacement for
uuencode with the advantage that it only incurred a 5/4ths expansion instead
of 4/3rds.  Was there some reason why MIME didn't use btoa?
Newsgroups: comp.mail.mime
From: eng10479@nusunix1.nus.sg (SO BOON PIN)
Subject: testing
Organization: National University of Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Thu, 17 Dec 1992 15:27:07 GMT

testing

Newsgroups: comp.mail.mime
From: eng10479@nusunix1.nus.sg (SO BOON PIN)
Subject: testing2
Organization: National University of Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Thu, 17 Dec 1992 15:28:52 GMT


Newsgroups: comp.mail.mime