From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 11 Oct 2005 12:49:50 +1000
From: Chris Collins <xfire-9fans@xware.cx>
To: erik quanstrom <quanstro@speakeasy.net>,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] [Fwd: road sign]
Message-ID: <20051011024950.GB28444@localhost.localdomain>
References: <4349E6B7.20008@lanl.gov>
	<ee9e417a0510101252x49d4b08ek34bc8f848dd41fc0@mail.gmail.com>
	<20051011015640.5EEA91AB1BD@dexter-peak.quanstro.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051011015640.5EEA91AB1BD@dexter-peak.quanstro.net>
User-Agent: Mutt/1.5.6+20040907i
Cc: 
Topicbox-Message-UUID: 997493ee-ead0-11e9-9d60-3106f5b1d025

erik quanstrom was once rumoured to have said:
> apple's mail program has sent some goofy mime headers. Note the
> "multipart/appledouble". this definately isn't part of the rfcs.

No, but the RFCs never really covered correct handling of 'forked'
binary files (such as those found on Macs).

appledouble encoding at least gives everybody else a hope of
compatability by dividing the data and resource forks into seperately
encoded streams, whilst still letting another mac reconstruct the
stream correctly at the other end.

C.