Well, there are some misconceptions which need clearing up.
>> UUencode for the Mac? Don't make me laugh. I'm a Mac user. If I get
>> a MIME file, the mailer automatically decodes it for me and produces a
>> nice little icon.
>
>I understand. Unfortunately, Macs are not the vast majority of
>computer users.
But Macs *are* very common amongst clueless newbies, who are exactly
the people who need FAQs.
>But you still can do it. I think the point is:
>
> Mac The rest of the world :) strange OSes (DOS, ...)
>
>uuencode avail. standard avail.
Uuencode is only "standard" on UNIX, and it's broken on most UNIXes
I've seen.
>MIME nice maybe impossible (*) avail.
MIME is available for UNIX, Mac, Amiga, Atari ST, and PC (Windows, DOS
and OS/2). I think that covers 99% of the systems out there which
newbies are likely to be using. There's a simple decoder in C which
you could compile on VMS; I'm not sure if there are better packages
for VMS, because I don't use that system.
>NOTE: (*) I know of sites who sill refuse to install MIME, and I can't
> blame them.
Why?
>> If uuencode worked, MIME would have used it.
>
>Please! uuencode honestly worked since '60, and I think you can
>make it wark on every platform, despite all the difficulties you
>had.
No, you can't. Uuencode uses characters which are dropped or mangled
by some existing network systems. That means you *can't* get it to
work, no matter what you have at the recipient's end, because the data
hasn't got through.
Anyway, enough.
mathew
[
Usenet Hypertext FAQ Archive |
Search Mail Archive |
Authors |
Usenet
]
[
1993 |
1994 |
1995 |
1996 |
1997
]
© Copyright The Landfield Group, 1997
All rights reserved