IETF Logo Mail Archive

Re: [Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission

Carsten Bormann <cabo@tzi.org> Tue, 27 July 2021 00:22 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660C33A0809 for <rfc-markdown@ietfa.amsl.com>; Mon, 26 Jul 2021 17:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vlNFO_Df4GRq for <rfc-markdown@ietfa.amsl.com>; Mon, 26 Jul 2021 17:22:42 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DA333A086C for <rfc-markdown@ietf.org>; Mon, 26 Jul 2021 17:22:42 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYcty4wH0z2xN0; Tue, 27 Jul 2021 02:22:34 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <F15694DF-6ACD-469F-9CA9-E33C5FC03223@mnot.net>
Date: Tue, 27 Jul 2021 02:22:34 +0200
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 649038154.0938981-f1ceb5d688f1525954838a31ae82bf52
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC5E00A5-2FBF-45E4-985B-5E67935D3192@tzi.org>
References: <20210712034838.B461E209AFFB@ary.qy> <6c781dab-7a40-7031-be1c-d77a182f4cf4@gmail.com> <DE0CD982-D4BE-44A6-9234-B53A756E9717@mnot.net> <bbb8302a-4041-35db-ce61-d2a18b8ebeee@taugh.com> <AB6E5013-C14E-4962-8907-17F241971F9D@tzi.org> <20210719171839.GB24216@faui48e.informatik.uni-erlangen.de> <DBCC4252-8A2D-473C-82CD-B1B2688586D3@tzi.org> <777A0822-6C16-4967-ABD0-BD35359B9FC5@tzi.org> <974739FF-7EB8-475B-A6A9-CB096D567E91@tzi.org> <10368632-F4A3-4876-A4F0-81C3DDBE002F@mnot.net> <F5519EBC-E453-4552-8B7F-F34425DAD2A1@tzi.org> <F15694DF-6ACD-469F-9CA9-E33C5FC03223@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/5GSlZd60jZYjjHW543Mbc_A92co>
Subject: Re: [Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2021 00:22:46 -0000

On 2021-07-27, at 02:17, Mark Nottingham <mnot@mnot.net> wrote:
> 
> 
> 
>> On 27 Jul 2021, at 10:13 am, Carsten Bormann <cabo@tzi.org> wrote:
>> 
>> On 2021-07-27, at 01:58, Mark Nottingham <mnot@mnot.net> wrote:
>>> 
>>> Thanks, Carsten! I've converted one of my drafts' toolchain to use this, and it seems to work well (with some differences in the XML, which is to be expected).
>> 
>> The XML left in the drafts repository by the current submission engine is the unconverted one.
> 
> Sorry, I don't understand?

The XML when you don’t convert before sending is the one that gets to the I-D repo, so it certainly will look different.

>>> One question: do you have any plans to tidy the XML output (e.g., with indentation, etc.)?
>> 
>> There actually is code to do some indentation.
>> 
>> There have never been bug reports on this, so it seems it is mostly non-functional now.
>> 
>> What are the requirements on that tidying?
> 
> Just aesthetic; if the XML is going to be the canonical format, it's nice if it's somewhat pretty.

But the RPC makes sure of that :-)

> Also, it reduces the chances of the RPC making unnecessary diffs in their work.

They will start from the v2v3 output, so there will be tons of diffs from an unconverted hybrid document.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email