From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/6139 Path: main.gmane.org!not-for-mail From: morioka@jaist.ac.jp (=?ISO-2022-JP?B?GyRCPGkyLBsoQiAbJEJDTkknGyhC?= / MORIOKA Tomohiko) Newsgroups: gmane.emacs.gnus.general Subject: Re: Suggestions Date: 05 May 1996 23:20:05 +0900 Organization: JAIST, Hokuriku / =?ISO-2022-JP?B?GyRCS0xOJkBoQzwySjNYGyhC?= =?ISO-2022-JP?B?GyRCNTs9UUJnM1gxIUJnM1gbKEI=?= Sender: morioka@is28e1s91.jaist.ac.jp Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.55) Content-Type: multipart/mixed; boundary="Multipart_Sun_May__5_23:20:05_1996-1" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035146638 2675 80.91.224.250 (20 Oct 2002 20:43:58 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:43:58 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id HAA05279 for ; Sun, 5 May 1996 07:43:30 -0700 Original-Received: from mikan.jaist.ac.jp ([150.65.8.6]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Sun, 5 May 1996 16:20:12 +0200 Original-Received: from is28e1s91.jaist.ac.jp (MORIOKA Tomohiko ) by mikan.jaist.ac.jp (8.7.5); id XAA22665; Sun, 5 May 1996 23:20:07 +0900 (JST) Original-Received: by is28e1s91.jaist.ac.jp (4.1/JE-C); Sun, 5 May 96 23:20:07 JST Original-To: ding@ifi.uio.no X-Emacs: Mule 2.3 =?ISO-2022-JP?B?KBskQkt2RSYyVhsoQik=?= based on 19.30 Dcc: morioka X-Mua: tm-mh-e 7.59, tm-view 7.57 In-Reply-To: Steven L Baur's message of 03 May 1996 23:11:10 -0700 Original-Lines: 65 X-Mailer: September Gnus v0.80/Emacs 19.30 Xref: main.gmane.org gmane.emacs.gnus.general:6139 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:6139 --Multipart_Sun_May__5_23:20:05_1996-1 Content-Type: text/enriched; charset=US-ASCII Steven> >>>>> "Per" == Per Abrahamsen < writes: Per> Actually, it is text/enriched. Too many people confused richtext Per> with some half-hearted and poorly defined attempt at a portable Per> word processor format created by Microsoft with a similar name. Per> But I think it worked, at least metamail (M-t) could decode the Per> message. --Multipart_Sun_May__5_23:20:05_1996-1 Content-Type: text/plain; charset=US-ASCII >>>>> In >>>>> Steven L Baur wrote: Steven> The code for it in tm is richtext.el, and the MIME type it put Steven> on that message was: Steven> Mime-Version: 1.0 (generated by tm-edit 7.53) Steven> Content-Type: text/richtext; charset=US-ASCII Steven> The copy I got was indeed enriched automatically by TM. Steven> Is text/enriched preferred then instead of text/richtext? My Steven> mailcap came with both defined identically, so I guess it Steven> could go either way. But if TM is using a suboptimal name, Steven> then now is the time to get it fixed. tm supports both text/enriched and text/richtext. Because an news reader for NeXT uses text/richtext. In fact, richtext support of tm was made for a NeXT user. After that, RMS requested me to use enriched.el. So I rewrote tm-rich.el to use enriched.el. However I supported text/richtext too for compatibility. RMS requested me to write text/richtext converter so I wrote richtext.el (however richtext.el wasn't bundled into Emacs :-P) Anyway, richtext.el requires enriched.el so it supports both formats. Maybe the name `richtext.el' is confusing. By the way, now enriched.el is included in Emacs 19.29 or later and XEmacs 19.14 or later. text/enriched is more readable than text/richtext. It uses ``n-1 rule'' instead of `' tag. ``n-1 rule'' is simple. N-1 line brakes is encoded to N line breaks. I think `text/enriched' is more readable than `_^Ht_^He_^Hx_^Ht_^H/_^He_^Hn_^Hr_^Hi_^Hc_^Hh_^He_^Hd'. So I think text/enriched is not so bad. Thanks, -- ---------------------------------------------------------------------- Morioka Tomohiko (`Morioka' is my family name, `Tomohiko' is my personal name.) ------- I protest resumption of French and Chinese nuclear testing.--- --Multipart_Sun_May__5_23:20:05_1996-1--