From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/18579 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: MIME composition (was: Storing the group a message has been written to) Date: 14 Nov 1998 00:02:29 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035157078 6893 80.91.224.250 (20 Oct 2002 23:37:58 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:37:58 +0000 (UTC) Return-Path: 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 SAA29563 for ; Fri, 13 Nov 1998 18:01:20 -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 RAB09841; Fri, 13 Nov 1998 17:00:53 -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:00:43 -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 RAA05607 for ; Fri, 13 Nov 1998 17:00:32 -0600 (CST) Original-Received: from sparky.gnus.org (ppp034.uio.no [129.240.240.35]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id SAA29534 for ; Fri, 13 Nov 1998 18:00:22 -0500 (EST) Original-Received: (from larsi@localhost) by sparky.gnus.org (8.8.5/8.8.5) id AAA15557; Sat, 14 Nov 1998 00:03:56 +0100 Mail-Copies-To: never X-Now-Reading: Janet Frame's _The Carpathians_ X-Now-Playing: Eurythmics's _Sweet Dreams (Are Made Of This)_ Original-To: ding@gnus.org In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "13 Nov 1998 23:45:15 +0100" User-Agent: Gnus/5.070043 (Pterodactyl Gnus v0.43) Emacs/20.3 X-Face: &w!^oO~dS|}-P0~ge{$c!h\ I don't think your mechanism is restricted to multipart/mixed. You > could code the nesting in the part numbers (1.2.3 is the third part in > the second part of the first part). You could put information on > whether it's multpart/alternative or multipart/mixed or > multipart/whatever either in the gruft that goes at the end of the > buffer, or in the button itself. Yes, but how would the user specify what goes in the multipart/alternative bits? If I want to send the following message as a multipart/alternative (if I'm in a disassociative mood): ------------- You are so great. ------------- Content-Type: text/richtext You suck! ------------- How would I do this? And would I ever want to do this? I can't imagine ever using multipart/alternative, but perhaps that's just me... Or perhaps people use multipart/alternative if they compose things in a non-text/plain language (say, HTML) and want to generate an automatic text/plain alternative for those people who can't read that other language? In that case, this is moot, since that would be an automatic translation that doesn't require any user interface. > There's another problem with your suggestion. Suppose users > inadvertently edit the button? But maybe that's more of a feature > than a bug :-) > > Though users shuffling around the buttons manually will screw up the > nesting relationship big time. Indeed. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen