From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/18580
Path: main.gmane.org!not-for-mail
From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Newsgroups: gmane.emacs.gnus.general
Subject: Re: MIME composition (was: Storing the group a message has been written to)
Date: 14 Nov 1998 00:27:34 +0100
Sender: owner-ding@hpc.uh.edu
Message-ID: <vaf1zn7xjfd.fsf@ramses.cs.uni-dortmund.de>
References: <vafpvauv0v5.fsf@ramses.cs.uni-dortmund.de> <m3ogqbpgzz.fsf@sparky.gnus.org> <x77lwz9t9n.fsf@des.castles.com> <m3ww4zs0c9.fsf@sparky.gnus.org> <vafpvarfc04.fsf@ramses.cs.uni-dortmund.de> <m3emr7rybd.fsf@sparky.gnus.org>
NNTP-Posting-Host: coloc-standby.netfonds.no
X-Trace: main.gmane.org 1035157079 6894 80.91.224.250 (20 Oct 2002 23:37:59 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Sun, 20 Oct 2002 23:37:59 +0000 (UTC)
Return-Path: <owner-ding@hpc.uh.edu>
Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1])
	by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id SAA00268
	for <jason@mailhost.sclp.com>; Fri, 13 Nov 1998 18:29:21 -0500 (EST)
Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5])
	by karazm.math.uh.edu (8.9.1/8.9.1) with ESMTP id RAB10603;
	Fri, 13 Nov 1998 17:29:09 -0600 (CST)
Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 13 Nov 1998 17:27:51 -0600 (CST)
Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id RAA05976 for <ding@hpc.uh.edu>; Fri, 13 Nov 1998 17:27:43 -0600 (CST)
Original-Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42])
	by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id SAA00200
	for <ding@gnus.org>; Fri, 13 Nov 1998 18:27:37 -0500 (EST)
Original-Received: from ramses.informatik.uni-dortmund.de (ramses.cs.uni-dortmund.de [129.217.20.180]) by waldorf.cs.uni-dortmund.de  with SMTP id AAA03871 for <ding@gnus.org>; Sat, 14 Nov 1998 00:27:35 +0100 (MET)
Original-Received: (grossjoh@localhost)
	by ramses.informatik.uni-dortmund.de id AAA06541; Sat, 14 Nov 1998 00:27:34 +0100
Original-To: ding@gnus.org
In-Reply-To: Lars Magne Ingebrigtsen's message of "14 Nov 1998 00:02:29 +0100"
Original-Lines: 25
User-Agent: Gnus/5.070042 (Pterodactyl Gnus v0.42) Emacs/20.3
Precedence: list
X-Majordomo: 1.94.jlt7
Xref: main.gmane.org gmane.emacs.gnus.general:18580
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:18580

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

  > Yes, but how would the user specify what goes in the
  > multipart/alternative bits?

The problem of delimiting `inline' parts occurs even with flat
multipart/mixed.

Let's say you have two kinds of buttons: inlined buttons and
attachment buttons.

Thus, "{{{ 1.3 text/plain }}}" would mark the beginning of an inlined
text/plain part, whereas "[[[ 1.4 text/html ]]]" would mark the
beginning of an attached text/html part (to be found at the end of the
buffer, made invisible by narrowing, as you suggest).

For the inline case, a part begins at its button and ends at the next
button or (point-max).

Of course, if users want to use text which looks like a button, they
lose.

kai
-- 
Life is hard and then you die.