From: dsg@mitre.org (David S. Goldberg)
Subject: Re: Mime question - viewing sent html pages
Date: 08 Nov 1999 13:39:08 -0500 [thread overview]
Message-ID: <m1baeoo7rqr.fsf@blackbird.mitre.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "08 Nov 1999 09:26:48 +0100"
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>> Hm. There is also mm-inlined-types, which contains "text/.*".
>> Maybe it helps to remove that item from the variable and to add
>> "text/plain", instead?
>>
>> Why does Gnus inline a type which can't be inlined? Strange.
> The MIME RFCs say that all text/* parts that can't be grokked should
> be displayed anyway. That's the difference between text/* parts
> and, say, application/* -- the text/* parts should remain
> (theoretically) legible to a human bean even if the kompooter
> doesn't quite know how to deal with them.
Bummer. That sounds like the patches I sent out a couple weeks ago
creating mm-inline-override-types et al screw up MIME compliance.
Sigh.
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next prev parent reply other threads:[~1999-11-08 18:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-04 1:52 David Maslen
1999-11-04 8:19 ` Steinar Bang
1999-11-04 15:21 ` David Maslen
1999-11-05 10:27 ` Steinar Bang
1999-11-05 11:20 ` David Maslen
1999-11-07 1:19 ` Lars Magne Ingebrigtsen
1999-11-07 13:16 ` Kai Großjohann
1999-11-07 15:17 ` David Maslen
1999-11-07 16:30 ` Kai Großjohann
1999-11-08 0:11 ` David Maslen
1999-11-08 8:17 ` Kai Großjohann
1999-11-08 8:26 ` Lars Magne Ingebrigtsen
1999-11-08 18:39 ` David S. Goldberg [this message]
1999-11-08 19:35 ` David S. Goldberg
1999-11-08 8:28 ` Lars Magne Ingebrigtsen
1999-11-08 16:39 ` Robin S. Socha
1999-11-07 15:17 ` David Maslen
1999-11-07 21:00 ` Lars Magne Ingebrigtsen
1999-11-07 21:18 ` Eric Marsden
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=m1baeoo7rqr.fsf@blackbird.mitre.org \
--to=dsg@mitre.org \
/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).