Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Improper handling of some mime types
Date: Thu, 14 Feb 2002 13:38:29 -0500	[thread overview]
Message-ID: <2nzo2bx61m.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <m2664zdipf.fsf@kurt.swanson> (Kurt Swanson's message of "14 Feb 2002 10:25:16 -0800")

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


[...]

>> 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.
>
> I believe it's the latter...

It is

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

Gnus rendering is correct too.

ShengHuo



  parent reply	other threads:[~2002-02-14 18:38 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
     [not found]       ` <m2664zdipf.fsf@kurt.swanson>
2002-02-14 18:38         ` ShengHuo ZHU [this message]
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=2nzo2bx61m.fsf@zsh.cs.rochester.edu \
    --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).