IETF Logo Mail Archive

Re: [xml2rfc] Current xml2rfc produces errors on published RFCs

Carsten Bormann <cabo@tzi.org> Mon, 02 August 2021 16:58 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9CD33A0E60 for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 09:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 kbTL2FOFgAP7 for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 09:58:34 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.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 352913A0E5F for <xml2rfc@ietf.org>; Mon, 2 Aug 2021 09:58:34 -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 4GdkjK4xXDz2xKK; Mon, 2 Aug 2021 18:58:28 +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: <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
Date: Mon, 02 Aug 2021 18:58:22 +0200
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 649616301.944831-f8e47cca92cc6a0f6ac19cc09c6d29c3
Content-Transfer-Encoding: quoted-printable
Message-Id: <F36D2C8E-E5B5-45C7-BA32-A553E2B4C727@tzi.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <98df983-bf39-6521-dffe-86e44015db7f@taugh.com> <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Zyv-LudhhTSv1iQa553-Y5SP3Wg>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 16:58:39 -0000

On 2021-08-02, at 18:42, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> So if anything breaks with published canonical XML, we can't make that
> change?

I’d say, if a function of xml2rfc breaks that we need to run-on published v3 RFCs (8650+), we should make a better change.

Re-rendering is certainly one such function.
What else?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email