From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] [Fwd: road sign]
Date: Mon, 10 Oct 2005 22:05:38 -0500 [thread overview]
Message-ID: <BBFE8564-57E3-40B5-AAE7-574AE8DF8A0B@corpus-callosum.com> (raw)
In-Reply-To: <20051011024950.GB28444@localhost.localdomain>
On Oct 10, 2005, at 9:49 PM, Chris Collins wrote:
> 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).
Thankfully, even Apple on OS X has slowly gone away from the blasted
Resource Forks. Sure, you can still use them (if you're Adobe), but
none of the Cocoa or CoreFoundation APIs go out and encourage to
resource forks any more.
That said, Mail.app does show it's NeXTMail heritage and do some
things that make other people and mail transports a little mad. But,
at least it doesn't force in line breaks like the other evil empire's
mail program. I've spent too much time having to talk people through
a URL that gets broken w/ a LF/CR breaking it in two.
jas
next prev parent reply other threads:[~2005-10-11 3:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 3:57 Ronald G Minnich
2005-10-10 19:52 ` Russ Cox
2005-10-11 1:56 ` erik quanstrom
2005-10-11 2:34 ` erik quanstrom
2005-10-11 2:49 ` Chris Collins
2005-10-11 3:05 ` Jeff Sickel [this message]
2005-10-11 5:52 ` David Leimbach
2005-10-11 7:11 ` Chris Collins
2005-10-11 8:05 ` leimy2k
2005-10-11 7:25 ` Uriel
2005-10-11 10:05 ` erik quanstrom
2005-10-13 2:09 ` Jeff Sickel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BBFE8564-57E3-40B5-AAE7-574AE8DF8A0B@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).