From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/23935 Path: main.gmane.org!not-for-mail From: davidk@lysator.liu.se (David =?iso-8859-1?q?K=E5gedal?=) Newsgroups: gmane.emacs.gnus.general Subject: Re: MIME variables Date: 06 Jul 1999 23:41:34 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: References: <87so74o1dp.fsf@pc-hrvoje.srce.hr> <874sjjdyqo.fsf@pc-hrvoje.srce.hr> <87lncvcid9.fsf@pc-hrvoje.srce.hr> <87zp194xl4.fsf@pc-hrvoje.srce.hr> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035161576 5876 80.91.224.250 (21 Oct 2002 00:52:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:52:56 +0000 (UTC) Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id RAA13824 for ; Tue, 6 Jul 1999 17:43:51 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id QAB19685; Tue, 6 Jul 1999 16:42:09 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 06 Jul 1999 16:42:58 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id QAA29291 for ; Tue, 6 Jul 1999 16:42:48 -0500 (CDT) Original-Received: from samantha.lysator.liu.se (root@samantha.lysator.liu.se [130.236.254.202]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id RAA13771 for ; Tue, 6 Jul 1999 17:41:45 -0400 (EDT) Original-Received: from venom.lysator.liu.se (venom.lysator.liu.se [130.236.254.19]) by samantha.lysator.liu.se (8.9.3/8.9.3) with ESMTP id XAA28800; Tue, 6 Jul 1999 23:41:35 +0200 (MET DST) Original-Received: (from davidk@localhost) by venom.lysator.liu.se (980427.SGI.8.8.8/8.8.7) id XAA55317; Tue, 6 Jul 1999 23:41:35 +0200 (CEST) Original-To: ding@gnus.org In-Reply-To: Lars Magne Ingebrigtsen's message of "06 Jul 1999 18:01:15 +0200" Original-Lines: 59 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:23935 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:23935 Lars Magne Ingebrigtsen writes: > Hrvoje Niksic writes: > > > > text/x-patch would perhaps be better? That would mean that they are > > > human-readable, but not plain. > > > > Probably. Yes. > > I'm just off for bed, but does the MIME RFC's say anything in > particular about doing stuff like text/x-patch? I know that it's > common to do application/x-whatever, but I don't really recall seeing > many x-whatevers as subtypes of the text type... Looking at RFC 2045, I see tht the BNF grammar allows subtypes of the x-* variety. Scanning quickly through the document, I see no other restrictions. RFC 2046 has the following to say about text/*: (1) text -- textual information. The subtype "plain" in particular indicates plain text containing no formatting commands or directives of any sort. Plain text is intended to be displayed "as-is". No special software is required to get the full meaning of the text, aside from support for the indicated character set. Other subtypes are to be used for enriched text in forms where application software may enhance the appearance of the text, but such software must not be required in order to get the general idea of the content. Possible subtypes of "text" thus include any word processor format that can be read without resorting to software that understands the format. In particular, formats that employ embeddded binary formatting information are not considered directly readable. A very simple and portable subtype, "richtext", was defined in RFC 1341, with a further revision in RFC 1896 under the name "enriched". [...] The canonical form of any MIME "text" subtype MUST always represent a line break as a CRLF sequence. Similarly, any occurrence of CRLF in MIME "text" MUST represent a line break. Use of CR and LF outside of line break sequences is also forbidden. This rule applies regardless of format or character set or sets involved. [...] 4.1.4. Unrecognized Subtypes Unrecognized subtypes of "text" should be treated as subtype "plain" as long as the MIME implementation knows how to handle the charset. Unrecognized subtypes which also specify an unrecognized charset should be treated as "application/octet- stream". -- David Kågedal http://www.lysator.liu.se/~davidk/