On 9/18/01 2:44 PM, Barry Wainwright deftly typed out:
>> Actually, I would consider Entourage to be more in conformity with standards
>> and practice than Eudora in this case. Having/requiring a file with an
>> ambiguous file type (TEXT) as Eudora does is not consistent with the
>> expected Macintosh user experience.
>>
>
> Except that it is strictly true, since the data is pure ascii, and therefore
> type TEXT suits just fine :)
I believe the reason there are people in two opposite camps on this issue is
that they both have arguably valid points. I, however, fall in the E'rage
camp on this one.
Entourage could very well assign the type "TEXT" to exported mailboxes to
further aid in the *export* of said mailbox. However, there not being any
standard file type associated with mbox files giving it a "MBOX" file type
aids in the re-importing of previously exported data. Since Entourage is the
application that did the exporting it has a right to ease it's
re-assimilation of the data.
Eudora on the other hand would be aided by the file type "TEXT" on exported
Entourage mailboxes since that is what it is used to. However, mbox files
don't have to have a file type. What if you FTP an mbox file from a Unix
server in binary mode? You would have no file type associated with the file.
Does Eudora require you to change the file type of these mbox files to
"TEXT"? I don't actually know. I think I remember that it *does* require you
to change the line endings. I believe that Eudora should allow the import of
mbox files of any file type (as does Entourage). Being able to double-click
the mbox is another issue. For importing, the application should be lenient
in requiring data that cannot be counted on to be as expected (such as the
file type).
Just my 2 pennies.
-Remo Del Bello
--
"Alcohol & calculus don't mix. Never drink & derive."
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
