Gnus development mailing list
 help / color / mirror / Atom feed
From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Ist multipart/mixed really correct?
Date: Sun, 24 Aug 2003 23:51:04 +0200	[thread overview]
Message-ID: <m37k52wwun.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <m3y8xissds.fsf@defun.localdomain>

On 24 Aug 2003, Jesper Harder <- harder@myrealbox.com wrote:

> sigurd@12move.de (Karl Pflästerer) writes:

>>> sigurd@12move.de (Karl Pflästerer) writes:

>>>> Gnus declares the posting as multipart/mixed but according to rfc 2046
>>>> multipart/parallel seems to be the correct alternative. WDYT?

>> I you have a posting with different charcter encodings which can't
>> be unified you get multipart/mixed.

> I don't think multipart/parallel is the correct type for this
> circumstance.  RFC 2046 says:

> ,----
> |    In particular, in a parallel entity, the order of body parts is
> |    not significant.
> | 
> |    A common presentation of this type is to display all of the parts
> |    simultaneously on hardware and software that are capable of doing
> |    so.
> `----

> Clearly, the order of the parts _is_ significant in this case.  We
> wouldn't want all of the parts to be popped up in different windows as
> the RFC suggests is a common way of representing
> multipart/alternative.

I think you are right.  I will answer in the other group in that manner.

   KP

-- 
 He took his vorpal sword in hand:
     Long time the manxome foe he sought--
 So rested he by the Tumtum tree,
     And stood awhile in thought.  "Lewis Carroll" "Jabberwocky"



      reply	other threads:[~2003-08-24 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-24 18:09 Karl Pflästerer
2003-08-24 18:36 ` iMeowbot
2003-08-24 19:32 ` Jesper Harder
2003-08-24 19:58   ` Karl Pflästerer
2003-08-24 20:38     ` Jesper Harder
2003-08-24 21:51       ` Karl Pflästerer [this message]

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=m37k52wwun.fsf@hamster.pflaesterer.de \
    --to=sigurd@12move.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).