Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: funny multipart/related not displaying correctly
Date: 21 Feb 2001 01:29:37 -0500	[thread overview]
Message-ID: <2nu25oblbi.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <87r90sr33l.fsf@julian.uwo.ca> (Dan Christensen's message of "21 Feb 2001 00:56:30 -0500")

Dan Christensen <jdc@uwo.ca> writes:

> The message attached below isn't displayed well by Gnus.  I suspect
> that it is incorrect MIME.  Unfortunately, I'm getting a lot of
> messages like this from a certain source who can't change the software
> which generates them.  So I'm wondering:  are they in fact incorrect
> MIME, and is there a way to get Gnus to detect this and display them
> properly automatically?
> 
> The messages consist of a multipart/related with
> type="multipart/alternative" and two sub-parts.  The first subpart
> (part 1) is a multipart/alternative (which is correct) and the second
> (part 2) is an image (replaced below by a text/plain part).  The
> enclosing multipart/related shouldn't be an alternative; I want to see
> one of the first two parts and the last part.  If I hit `K m', Gnus
> somehow can tell this is what I want and fixes the message.  I'd like
> this to happen automatically.

> By the way, before being fixed, `K b' only shows one button, which
> corresponds to part 1, the alternative.  But I never see part 2.  
> `C-u K b' fixes this, but shouldn't I see an alternative to part 1
> with `K b'?
> 
> `C-d' on the message shows the correct heirarchy of parts.

gnus-mime-display-multipart-as-mixed is the variable, but maybe you
don't want multipart/alternative displayed as mixed. So, I just added
gnus-mime-display-multipart-related-as-mixed and
gnus-mime-display-multipart-alternative-as-mixed.

ShengHuo



  reply	other threads:[~2001-02-21  6:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21  5:56 Dan Christensen
2001-02-21  6:29 ` ShengHuo ZHU [this message]
2001-02-22  2:20   ` Dan Christensen
2001-02-24  4:02     ` ShengHuo ZHU

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=2nu25oblbi.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.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).