Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Improper handling of some mime types
Date: Thu, 14 Feb 2002 18:25:16 +0100	[thread overview]
Message-ID: <vafwuxg6kn7.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m26650dmsa.fsf@kurt.swanson> (Kurt Swanson's message of "14 Feb 2002 08:57:09 -0800")

Kurt Swanson <direct@reply.not.desired> writes:

> So you're saying I essentially have to hit `K b' in every single
> article I read just in case there's (by Gnus) hidden data, and then,
> if there is an html version, choose that, and the click all buttons,
> hoping one of them will do something useful for me?

> To me this is a *serious* error.  There are two mime parts in
> message-id: tQCa8.5559$qt6.469306@newsread2.prod.itd.earthlink.net in
> the alt.binaries.pictures.orchid newsgroup.  To put it simply, there
> is part 1a, 1b, and 2; i.e. there are two versions of part one (they
> share the same id code) and one part 2 (different id).  Part two
> should be recognized as separate (and equal?) and displayed,
> regardless of the user's choice of a or b for part 1.  The fact that
> part 2's very existence can only be seen (and then handled poorly)
> when part 1b is chosen can't be the desirable functionality here...
>
> Please go and check out this article yourself...

I can't do that, for I can't find a server hosting that group.
Sorry.  (I tried Google, did I do something wrong there?)

Whether Gnus is in error depends on the structure of the message.  It
could be like this (using pseudo-XML):

    <part type="multipart/alternative">
      <part type="text/plain"/>
      <part type="multipart/related">
        <part type="text/html"/>
        <part type="image/png"/>
      </part>
    </part>

It could also look like this:

    <part type="multipart/mixed">
      <part type="multipart/alternative">
        <part type="text/html"/>
        <part type="text/plain"/>
      </part>
      <part type="image/png"/>
    </part>

Your description sounds like the first variant, and then the Gnus
rendering would be correct.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)



  parent reply	other threads:[~2002-02-14 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2wuxgg8ab.fsf@kurt.swanson>
2002-02-14  8:35 ` Kai Großjohann
     [not found]   ` <m26650dmsa.fsf@kurt.swanson>
2002-02-14 17:25     ` Kai Großjohann [this message]
     [not found]       ` <m2664zdipf.fsf@kurt.swanson>
2002-02-14 18:38         ` ShengHuo ZHU
2002-02-14 17:32     ` ShengHuo ZHU
2002-02-14 17:39     ` David S. Goldberg
2002-02-14 17:54     ` David S. Goldberg
     [not found]       ` <m2adubdis3.fsf@kurt.swanson>
2002-02-15  9:09         ` Kai Großjohann
2002-02-14 18:00     ` Karl Kleinpaste

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=vafwuxg6kn7.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).