IETF Logo Mail Archive

Re: [rfc-i] The upcoming transition to xml2rfc v3

Jim Schaad <ietf@augustcellars.com> Fri, 06 September 2019 16:26 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35262120125 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 6 Sep 2019 09:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.951
X-Spam-Level:
X-Spam-Status: No, score=-4.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 tE1IgvZQzNdk for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 6 Sep 2019 09:26:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDD591200C7 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 6 Sep 2019 09:26:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5315EB80B2D; Fri, 6 Sep 2019 09:26:29 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id C89D1B80B28; Fri, 6 Sep 2019 09:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJKzJ_EcIDqq; Fri, 6 Sep 2019 09:26:26 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) by rfc-editor.org (Postfix) with ESMTPS id 2D04EB80B22; Fri, 6 Sep 2019 09:26:26 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 6 Sep 2019 09:26:20 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Julian Reschke' <julian.reschke@gmx.de>, 'RFC Editor' <rfc-editor@rfc-editor.org>, 'RFC Interest' <rfc-interest@rfc-editor.org>
References: <20190906042325.GC12952@rfc-editor.org> <04c001d56478$21b94220$652bc660$@augustcellars.com> <5c9530d8-909b-7004-7e2e-e598efdceccd@gmx.de>
In-Reply-To: <5c9530d8-909b-7004-7e2e-e598efdceccd@gmx.de>
Date: Fri, 06 Sep 2019 09:26:20 -0700
Message-ID: <04d701d564cf$d2b0aee0$78120ca0$@augustcellars.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHjiufJjR1py0XrsfdtwsZCpnWvYQEaU4buAfCBdE6m6jMWkA==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Subject: Re: [rfc-i] The upcoming transition to xml2rfc v3
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: "'RFC ISE (Adrian Farrel)'" <rfc-ise@rfc-editor.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

This is a Carsten draft - so yes he is aware of it.

-----Original Message-----
From: Julian Reschke <julian.reschke@gmx.de> 
Sent: Thursday, September 5, 2019 11:11 PM
To: Jim Schaad <ietf@augustcellars.com>; 'RFC Editor' <rfc-editor@rfc-editor.org>; 'RFC Interest' <rfc-interest@rfc-editor.org>
Cc: 'RFC ISE (Adrian Farrel)' <rfc-ise@rfc-editor.org>
Subject: Re: [rfc-i] The upcoming transition to xml2rfc v3

On 06.09.2019 07:58, Jim Schaad wrote:
> Will the RFC Editor potentially be editing output to make the v3 vocabulary look cleaner?  I know of a kramdown file that is having some formatting problems, at least in part due to how it is creating the xml file.
>
> Jim

Would be good to have more details. Is this a kramdown2629 issue? Is Carsten aware?

Best regards, Julian

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email