IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Mon, 02 August 2021 16:42 UTC

Return-Path: <julian.reschke@gmx.de>
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 01FC43A0D38 for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 09:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.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 V6RFh6Io_w-F for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 09:42:20 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 A28403A0D34 for <xml2rfc@ietf.org>; Mon, 2 Aug 2021 09:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627922536; bh=Hnp11pvtje9wiBaOZtwFjAfq1kUG6IcpmRiHoW2qkb8=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=TFgGnWOx16dzz8Su9NSAy2jmcjjD2BHwhKjUCBvcgngnML06bqpi8f+oOYDChE6xl 4mJk6jHBl4tF9jtNEn1nMO9wuDjnoMhShCycW6nVz+6vBVLuhfRPosM/ukboNddm9m DjSkyyXjzj0jnAMPMhaCRxEHABj9Njc3YH8zgXOg=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.1.70] ([212.205.152.82]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MuDbx-1n0mvd0PID-00uZiM for <xml2rfc@ietf.org>; Mon, 02 Aug 2021 18:42:16 +0200
To: xml2rfc@ietf.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>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
Date: Mon, 02 Aug 2021 18:42:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <98df983-bf39-6521-dffe-86e44015db7f@taugh.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:nnOuf2JqbdgXprRiuaYUjBFeykSSCz2wQwPGtQ5OqY0FZGgt8nE iFEbkFG0qT1xpg0TAQ2//Zz5TFaiqXHE3eFR+BfLkhwLYfoSUaOzeV6bkhXIbWUjNJPqDuw FXh3ShEskl3Zlku9jet7qjESu96X+BAUTxy0v+j3jHVnxYncGXIch7m1cTuXNLl3aM7STCa kZkEYU32sCnL9+nWyxm3Q==
X-UI-Out-Filterresults: notjunk:1;V03:K0:CYIcfZi+AWo=:MVf8GFm7UXi0NrxkeE4/om SVfH1HCPCL5u1i437fOZnhiuQSCNdh1szeKpGwU/oGFD9spGb3MpF4H4Q1BOBYo/H+MUXF5DU Rnr5nEXAY3s8nA8THVT6+a2xnHidExQBbnsuGvBrecebctrz3prK5yhAbMFczAcQ9JUMANq39 3EKpvU1+Z1FKeDwh3a3l3Zd+GSmCSUdM74Ffbw9Om5axQh/uYgnbcwS1qnTrzfPmvTdF/FwvA ud7UB6d3QAzM54s1Qr1edQpiG4KlUMNVChsVPjrSThVbmX5ks+l8tw7M/f8gdGD1kaHgX5VsD RyLS+jnB/6otcBJw+HcOQOgX5zznUDO96qQdXOz8as1ZwWXMTQBN1og0g20k/aSgmB2q/y+gH ft4w+c3RzJOLwCooNYLbCW0TCCq6cxh69fedEy98KqI2cwcgpjiaL38uRMab7nRj5EABfxQJm X8HAqhWsRNHQ4S7UT4zRxP8FlJ3qSICtQo8RGVquimozd0GGa+epDx3N3g9tpFvcU9IQMjw7w S7pI37ASRjxcoPagKRx4TzZyH6MNkmKfBtJfe1jh+3yBmu9f3PA0+QtcoL5ogg/RLPuo44TiM 8VO1MQwrqu09tXJ6sgFCW9+Ovnn0hc66VMmpAtbBdgE2avRSoh14lwOJ+/CGG6mkI0wWNK6hC OB2C04AyQus2GB8xLCjMs2ZQhAsGPLhpKgWupNNT2ZkXdMGppswoolM0OrKcBcQud4gC97Kbr THRCcGlF8q5VJqXHQGOA+o0XDPEL3E/TdtMYJvsrxdQZGg6BH8ceCl1DYdLUZLPs/7yfStjRA aXt/NwZrT7A6J63C5/RHbUPQr+KuzdnwC+JDNgyJpLWP7whCHEitPPdwcV/X1a+ep6XUbst/J 4abHTt0VDHmLTiQLaa9G5c0eXjRcFuHk6AIsMRA/SacQhKRRd8fi3XLTTJ/3V89za/U1Z51dH gBlFCZXK58RwofCwqVOM61d2ZJhs9/6uJnpbXiZ+Rd+6+GxeNQJsS4xe7N6C/XC1udM2mtqCJ El27EF6L6OXLzOV9hT3upRPDTKshAgK0ulMV1LTqQ0whXbG0TGF0By3q2JPOP7Yoacj2rBPDU f3DNbZGx9mrdslm0Zkl8Xs0z63CEYgtLfdc704+y85FdmtyQo6hPOvVOA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/tXRCifvNQUQ2xvg8nSjvVnZaUAI>
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:42:26 -0000

Am 02.08.2021 um 17:25 schrieb John R Levine:
> On Mon, 2 Aug 2021, Martin J. Dürst wrote:
>>> When I run rfc8799.xml or rfc9001.xml through the current version of
>>> xmlrfc, it says:
>>>
>>> Error: Found no element to match the <xref> target attribute
>>> 'section-a.1'
>>>
>>> When I look at the XML, the target is there and this presumably
>>> worked when the RFCs were published.
>>
>> I think it would be a good idea to add the above two documents to a
>> test suite to avoid regressions. And use some kind of continuous
>> integration testing (if that's already done, that's great).
>
> Not just those two, all of them.  I've run the entire set of published
> RFCs through xml2rfc.  It takes maybe half an hour.  We definitely
> should do that before releasing each new version.

So if anything breaks with published canonical XML, we can't make that
change?

Best regards, Julian

v2.23.0 | Report a Bug | By Email