IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Mon, 02 August 2021 12:04 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 CFE463A1A81 for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 05:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 85xW9r1g9g6g for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 05:03:56 -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 B10D63A1A7A for <xml2rfc@ietf.org>; Mon, 2 Aug 2021 05:03:56 -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 4Gdc9P3LXCz2xJ5; Mon, 2 Aug 2021 14:03:53 +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: <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de>
Date: Mon, 02 Aug 2021 14:03:52 +0200
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, xml2rfc <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 649598631.553569-67abe4eca030b61bf3e26ad793114bac
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B968E22-B4BC-47AF-9A4C-53015726CD2F@tzi.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de> <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com> <431c2076-46b8-c71f-86ea-4186dffeff7e@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/Jipcr3X9xkmIGAMyFe4jn7sSmq4>
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 12:04:03 -0000

On 2021-08-02, at 11:25, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> The issue is that the document uses xref/target to point to sections
> indentified by their "pn" attribute, and that one's value is different
> under the new version of xml2rfc (and gets replaced).

So you need to unprep the xml before any further processing.

I’m not sure we have been told why there is a need to process the xml again; if there is authoring involved unprepping is already the right way to get rid of all that noise, so I don’t see how that is a big problem.

xml2rfc —unprep rfc8799.xml
… edit rfc8799.plain.xml
xml2rfc rfc8799.plain.xml

If this is just for generating renderings, of course xml2rfc should not second-guess the previous output of the preptool.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email