TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: MIME encoding From:Gurudutt Kamath/Technical Writing Centre <guruk -at- GIASBM01 -dot- VSNL -dot- NET -dot- IN> Date:Wed, 11 Dec 1996 17:37:47 +0530
Hello Iain and fellow professionals,
I sent a text file as an attachment to this list as well as Tekcom. In
Tekcom, the attachment was correctly displayed in PINE. Whereas in this
list there was the usual message about MIME and in PINE it showed a lot
of junk to my dismay. The worst part is it put the attachment in the body
of the email.
I quickly sent a Sorry for this "mess". I think all list owners should
provide information in FAQ as to the type of attachment accepatable and
its behaviour.
Best wishes to all
Guru
Technical Writing Centre, Mumbai (Bombay), India
"I edit_s_ users manuals." "i rights them 2."
(guruk -at- giasbm01 -dot- vsnl -dot- net -dot- in)
(http://members.tripod.com/~Kamath/index.html)
(Voice:91-22-886 21 83 Pager: 9624-215 911)
On Wed, 11 Dec 1996, Iain Harrison wrote:
>... personally I am not happy with MIME email.
> 1. There is no advantage in sending ASCII text MIME encoded, so there is
> no reason to have software that reads it - the converse is true in fact,
> but that's not a topic for here.
