Testing the waters for text/troff

duerst at w3.org (Martin Duerst) Tue, 03 January 2006 16:22 UTC

From: "duerst at w3.org"
Date: Tue, 03 Jan 2006 16:22:52 +0000
Subject: Testing the waters for text/troff
In-Reply-To: <200411221454.48418.blilly@erols.com>
References: <200411221454.48418.blilly@erols.com>
Message-ID: <6.0.0.20.2.20041123084754.05f1b608@localhost>
X-Date: Tue Jan 3 16:22:52 2006

I don't remember anything. I guess an explanation for this would
be that nroff/troff isn't usually passed to applications directly
(i.e. neither for mailers nor for browsers). But if you think it's
something you and others want to use, please go ahead and write a
draft. At the momement, I can't immagine anything that would lead
to a rejection of a well-written proposal. The main issues that
I can immagine (although I'm not an expert on ?roff stuff) you will
have to deal with would probably have to do with versioning.

Regards,    Martin.

At 04:54 04/11/23, Bruce Lilly wrote:
 >I am quite surprised that there is no registered MIME media type for
 >text with nroff/troff markup, especially as that format has traditionally
 >been used for RFC and Internet Draft documents (RFC 2223).  I
 >could find no record in the archives of this mailing list of any
 >discussion on the matter.  Has there been any proposal for such a
 >text subtype, and if so, what were the reasons that have prevented
 >it from being approved?