From: "John M. Aldrich" Newsgroups: comp.os.msdos.djgpp Subject: Re: (none) Date: Tue, 14 Oct 1997 19:30:44 +0000 Organization: Two pounds of chaos and a pinch of salt Lines: 29 Message-ID: <3443C864.4170@cs.com> References: Reply-To: fighteer AT cs DOT com NNTP-Posting-Host: ppp237.cs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Orlando Andico wrote: > > It might have occurred to you that some mailers automagically encode all > attachments (mine does -- PINE 3.96 for UNIX). Most of the Windows-based > mailers encode attachments as MIME by default. So it might not be the > previous poster's fault if he were unaware of this. In any case, words "MIME" is not an encoding scheme for files; it's a formatting standard for email and news messages. MIME-formatted messages can contain any type of content, from text to encoded binary, and even though the formatting may look strange to a non-compliant reader, it's still plain text. Most MIME-compliant mailers/posters can recognize the difference between a text and a binary file and only encode binaries. At the very least, there should be an option to turn encoding on or off for a given attachment. The original point is correct; uuencoded text is utterly ridiculous, and anybody with more than five minutes of Usenet experience ought to know that. It could have been expressed a bit more politely, though. -- --------------------------------------------------------------------- | John M. Aldrich | "Always listen to experts. They'll | | aka Fighteer I | tell you what can't be done, and why.| | mailto:fighteer AT cs DOT com | Then do it." | | http://www.cs.com/fighteer | - Lazarus Long | ---------------------------------------------------------------------