From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Displaying text/calendar after the text/html part
Date: Fri, 26 Jan 2024 07:55:14 +0100 [thread overview]
Message-ID: <87jznweg8d.fsf@dod.no> (raw)
In-Reply-To: <34603.7125958659$1706233277@news.gmane.org>
>>>>> Husain Alshehhi <husain@alshehhi.io>:
> Hello,
> By default, if I get an email that has two parts, text/html (first) and
> text/calendar (second), gnus by default shows the text/calendar. This
> default behavior is because mime tools in emacs display the latest part
> as it is the "most rich"[1]. However, in the case, both display
> different information. I would like to display the text/html first, and
> then the text/calendar at the same time. I would like to do that when
> the email has html and calendar parts. Is this possible?
Doesn't that depend on whether it is multipart/mixed or multipart/alternative?
With multipart/mixed:
https://datatracker.ietf.org/doc/html/rfc2046#section-5.1.3
The "mixed" subtype of "multipart" is intended for use when the body
parts are independent and need to be bundled in a particular order.
Any "multipart" subtypes that an implementation does not recognize
must be treated as being of subtype "mixed".
With multipart/alternative:
https://datatracker.ietf.org/doc/html/rfc2046#section-5.1.4
The "multipart/alternative" type is syntactically identical to
"multipart/mixed", but the semantics are different. In particular,
each of the body parts is an "alternative" version of the same
information.
I.e. with multipart/mixed both the calendar and text should be displayed
in the order they are found in the email, while with
multipart/alternative only the "richest" alternative should be
displayed?
next parent reply other threads:[~2024-01-26 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34603.7125958659$1706233277@news.gmane.org>
2024-01-26 6:55 ` Steinar Bang [this message]
2024-01-26 8:43 ` Eric S Fraga
2024-02-01 1:33 ` Husain Alshehhi
2024-01-26 1:40 Husain Alshehhi
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=87jznweg8d.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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).