Re: [Tools-discuss] Proposed survey on I-D authoring tools

worley@ariadne.com Thu, 01 October 2020 02:06 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F743A086B for <tools-discuss@ietfa.amsl.com>; Wed, 30 Sep 2020 19:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.985
X-Spam-Level:
X-Spam-Status: No, score=-0.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OESKZdV4SDD7 for <tools-discuss@ietfa.amsl.com>; Wed, 30 Sep 2020 19:06:39 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [69.252.207.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCED53A0870 for <tools-discuss@ietf.org>; Wed, 30 Sep 2020 19:06:38 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id NnfFkmgSaK61ANnyTkVYDY; Thu, 01 Oct 2020 02:05:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1601517937; bh=KU5thhr6O41R6Y9wRQBgmwjrcz4ggrlvnsb9uiA9FuM=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:MIME-Version:Content-Type; b=M/JWwBPb2UXOcFsddeINxXOp9hJkGmVZMKCnQVqHzhbYqfWyu9HsnGC2EVANrlgva LXjruPevXTufGCdsmhPrUF63bzSF1h8sWkxwhUYo3iqY7HEis7wME/BfWB9sFZL8aS vK7hS2vGrzuz485V+f8V6C4mCyY5PYsM61mMf9vizrM4RKaXzlypq5j/O91ymA1oA/ Zcm1e+R3RJ//Pa8DathGN0XdoDg7xOkQqn5C5EZj6kkMHYuUUlrWGTNfc247QNXVHV VJWneFMQ449bsjxpiLh6namUXlng4HfX/2CkCO4+zHT1xu7jN689khWmSFyP6u/gf5 doRBdpRIGNSYA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id NnyQk0072HWI7NnyQkfACL; Thu, 01 Oct 2020 02:05:35 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 09125Xpt002177; Wed, 30 Sep 2020 22:05:33 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 09125XMe002174; Wed, 30 Sep 2020 22:05:33 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Jay Daley <jay@ietf.org>
Cc: rfc-interest@rfc-editor.org, tools-discuss@ietf.org
In-Reply-To: <71CCD4C4-2CBA-4AD3-A254-2F19B261D882@ietf.org> (jay@ietf.org)
Sender: worley@ariadne.com
Date: Wed, 30 Sep 2020 22:05:33 -0400
Message-ID: <87mu1666qa.fsf@hobgoblin.ariadne.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/35aFzMMDvvTQBYTmvtzlgK3K2tQ>
Subject: Re: [Tools-discuss] Proposed survey on I-D authoring tools
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 02:06:41 -0000

Jay Daley <jay@ietf.org> writes:

> [QUESTION - Matrix/Rating Scale]
> How often have you used the following document format(s) and associated output process(es) (editor/template/converter) when authoring an I-D? (Ignore any you don’t know about)
> Items
> 	• Plain text using no markup
> 	• Plain text using a different output process
> 	• Markdown using the kramdown-rfc2629 converter
> 	• Markdown using the mmark converter
> 	• Markdown using the draftr converter
> 	• Markdown using the Pandoc2rfc converter
> 	• Markdown using a different output process
> 	• XML using the XMLMind editor and xml2rfc-xxe
> 	• XML using a different output process
> 	• AsciiDoc using the metanorma-ietf (formerly known as asciidoctor-rfc) converter
> 	• AsciiDoc using a different output process
> 	• TeX / LaTeX using Lyx editor and lyx2rfc
> 	• TeX / LaTeX using a different output process
> 	• nroff using the Nroff Edit editor
> 	• nroff using nroff2xml template
> 	• nroff using a different output process
> 	• Microsoft Word rich text using Joe Touch’s Word Template (RFC5385)
> 	• Microsoft Word rich text using a different output process (This means specifically using rich text styles that a template/convertor will recognise, it does not mean using this an editor for one of the other formats)
> 	• Other format (Only use this option if you author in a different format to all of those above) [PLEASE SPECIFY what format you author in and what output process you use]

There seem to be category inconsistency here.  It appears to me that the
major differentiator in this list is "What do you write the I-D in?",
viz., plain text, markdown, XML, AsciiDoc, TeX, nroff, MS Word.  Then
attached to that is "How do you output the I-D from that source?", which
seems to be "no markup", "a different output process", etc., etc.  And
then there's the element "What tool do you use to write the source?",
which can vary from completely unstated to tools specifically designed
to write I-Ds (e.g., Joe Touch's Word template).

What makes the choices hard to parse is that while all of the choices
contain the source file type, only some specify the editing tool, and
only some have the output process.  E.g., there are "XMLMind editor ->
XML -> xml2rfc", "XML -> a different output process", and "plain text",
each of which specifies a different subset of these elements.

Perhaps splitting out the three elements would make the choices clearer,
and possibly allow you to cover the universe of possibilities more
thoroughly.

Dale