On Sun, 20 Feb 2000 17:02:45 -0400, L.D. Best wrote:
> Don't blame Sam.
> His attachment on my e-mail came through the way it was supposed to.
> But on mail from my oldest son, yesterday, I got the same type of "I
> ain't gonna convert this so take a look" treatment from Arachne.
> NOW what??!!
> And, to answer Roger's question -- Arachne had no way of knowing that
> DIZ is a text file! So it was encoded.
> Glenn, or ??? Where do we add a line designating *.DIZ as text??
> l.d.
> ====
> On Sun, 20 Feb 2000 13:51:36 -0500, Roger Turk wrote:
>> Sam Heywood,
>> Here is how your "attached file, FILE_ID.DIZ is an ascii text file" came thru:
>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> P.S. BTW, the attached file, FILE_ID.DIZ is an ascii text file which
>> describes the program in Herr Muchsel's own words.
>> <snip>
<snipped encoded text file>
>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> The question is, why did an ASCII text file get encoded into a "base64"
>> encoded format?
Very good question. I took a look at this message before I sent it.
While it was still in my outbox, I clicked on the ikon representing
the attachment, and it opened and displayed just like any other text
attachment.
Sam Heywood
