on 3/03/2005 2:00 AM, Kyle DeMilo at [EMAIL PROTECTED] wrote: > If I were to send a file, on the Windows side, the person would receive the > file along with a much smaller, similarly named version of it as well. The > Windows people cannot open that smaller file. It used to happen with me all > the time with resumes.
<snip> While realising that I'm arguing from an n of 1, I've never seen the resource fork arrive through the mail. That would suggest that either the mail admins at the last couple of places I worked at were really switched on (no disrespect to the sysadmins on this list but this is not a likely option) or Exchange dumps them automatically. This from TidBITS#515/31-Jan-00 <http://db.tidbits.com/getbits.acgi?tbart=05787> ... AppleDouble breaks the Macintosh data and resource forks of a file apart, then attaches them separately to the message, at which point they're also Base64 encoded for transfer. When a modern Macintosh email program sees the two attachments, it decodes the Base64 and then reassembles them into a single file. When an email program on another platform sees the two attachments, it throws the resource fork away and decodes only the data fork, since other platforms don't understand Macintosh resource forks. >> From: David Wignall <[EMAIL PROTECTED]> >> Reply-To: "Entourage:mac Talk" <[email protected]> >> Date: Wed, 02 Mar 2005 22:00:28 +1300 >> To: Entourage mac Talk <[email protected]> >> Subject: Re: Recipients not able to open(encoding?) >> >> My understanding is that the encoded resource fork is simply ignored by >> Windows. Certainly that's what happens for me between home and work. >> AppleDouble is the 'best' encoding because of just this. > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
