[Tools-discuss] I-D/RFC source formats

Bruce Lilly <blilly@erols.com> Fri, 08 April 2005 19:22 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25846; Fri, 8 Apr 2005 15:22:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJzCN-0006z8-2M; Fri, 08 Apr 2005 15:31:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJz2D-0007IY-Jd; Fri, 08 Apr 2005 15:20:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJz29-0007IE-Pp; Fri, 08 Apr 2005 15:20:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25674; Fri, 8 Apr 2005 15:20:48 -0400 (EDT)
Received: from ns3a.townisp.com ([216.195.0.136] helo=ns3.townisp.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJzAx-0006s2-HD; Fri, 08 Apr 2005 15:29:56 -0400
Received: from mail.blilly.com (dhcp-0-8-a1-c-fa-f7.cpe.townisp.com [216.49.158.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "marty.blilly.com", Issuer "Bruce Lilly" (not verified)) by ns3.townisp.com (Postfix) with ESMTP id 5B36229939; Fri, 8 Apr 2005 15:20:47 -0400 (EDT)
Received: from marty.blilly.com (marty.blilly.com [192.168.99.98] (may be forged)) by mail.blilly.com with ESMTP id j38JKi3R025115(8.13.1/8.13.1/mail.blilly.com sendmail.mc.mail 1.23 2005/03/23 20:35:49) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) ; Fri, 8 Apr 2005 15:20:46 -0400
Received: from marty.blilly.com (localhost [127.0.0.1]) (authenticated (0 bits)) by marty.blilly.com with ESMTP id j38JKgsm025111(8.13.1/8.13.1/blilly.com submit.mc 1.3 2005/04/08 12:29:31) (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) ; Fri, 8 Apr 2005 15:20:44 -0400
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
To: ietf@ietf.org
Date: Fri, 08 Apr 2005 15:20:40 -0400
User-Agent: KMail/1.8
References: <200504081755.j38HtMPg013143@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200504081755.j38HtMPg013143@givry.rennes.enst-bretagne.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200504081520.40916.blilly@erols.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: IETF TOOLS discussion <tools-discuss@ietf.org>
Subject: [Tools-discuss] I-D/RFC source formats
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit

On Fri April 8 2005 13:55, Francis Dupont wrote:

>    and intuitively OpenOffice doesn't seem likely either.
> 
> => to prefer emacs to OOo is a subtle way to like open source (:-).

OOo is one of those that I mentioned doesn't seem to be able to
generate formatted plain text with appropriate parameters (in
addition to apparently not being able to generate RFC-specific
XML).

> => nroff is not so bad. The problem is the community which supported it
> moved to Latex many years ago...

Oh?  One of the reasons that I haven't used TeX (and things like LaTeX
which are layered on it) is the difficulty of getting suitable plain
text output.

> BTW IMHO the best tool should be so painful that 
> I-Ds would be very small (:-)?

The size of the boilerplate alone precludes that, unfortunately.  And
it gets worse next month when the secretariat stops accepting "he" (or
"she", as the case may be) as an alternative to "he or she" in that
boilerplate.

> PS: what we need is a rfc2xml. It seems there is a secret rfc2nroff...

Going from formatted RFC or draft to troff source is fairly easy. As
text will be re-flowed into paragraphs, it's mostly a matter of
inserting the right directives between paragraphs, for section
headings, etc. 

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/tools-discuss