IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 02 August 2021 05:10 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 5171D3A0919 for <xml2rfc@ietfa.amsl.com>; Sun, 1 Aug 2021 22:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 37pJxo5BmUFC for <xml2rfc@ietfa.amsl.com>; Sun, 1 Aug 2021 22:10:19 -0700 (PDT)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 999833A0918 for <xml2rfc@ietf.org>; Sun, 1 Aug 2021 22:10:19 -0700 (PDT)
Received: by mail-pj1-x102d.google.com with SMTP id k4-20020a17090a5144b02901731c776526so29800898pjm.4 for <xml2rfc@ietf.org>; Sun, 01 Aug 2021 22:10:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Ox1ZuBNe3+SuVNijCiTalg3PzrxSVjSGxx6zLZrKxTc=; b=AaoLCswedyM9zKI0YhP9/ORvE/jIR1BQhut6DySk2rIqgm9vylOJXtL44tMu123bH9 xjGKv84J2FeLTkd63dUnF+0rMVkWZ2pKPdeUhRiW5JB9fmEAWNYQd0oWDmR55JixSyL3 XdVhPP2gJeiACmUkKMx+htOkH1rs4iZBxcHAeYuVxulvWH85bZG97D7ToquKKHueX1Pk lFN8kLGNmhMyWuEW9naFS2tZNEcZaZxJJ15v62fmdI/9nL7f7B016s9yFPqsuAJBVeWp J7DDQJ+eg0zNOVy9VXYJcD49gCxs2YjRRAYZ5bdF81MdpjMbtJCrp9annfGg9CPYqvAR XdXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Ox1ZuBNe3+SuVNijCiTalg3PzrxSVjSGxx6zLZrKxTc=; b=anDtucv9nzR9NLuBRhwjnz4HE/zwYj9aL8ITTPItX7VUvVASN8pX9LL1e/mlDYe2iq IYRQC6PVSoDHTq2y7nBfdEZI5pr92uxP0J4VYPqLpHtO5Tkz6LoKrw29Nk88tsWGaum4 W+OD6YK4LClNCNIMzWkWGeFyp3pldOzBUfVhbZ3eWrVwVkuWJAqbrkPPXSRC99uNY91N TdngQ6A/B0q017OlZjLtbt+iHIBP/hjcqyxUSZ4gswrrf1YdKUuhPSLOC1i7yH1knfdB I1IZg4XkpcpbPntOz9lkYPZ1Mw7Y8ZmSXSAgSc4TSc/3CYFSuqu44FCCVzbLrxhTdcLX /rxA==
X-Gm-Message-State: AOAM532cCK+8a5hqL5aPa3qaQkrwO1ICkZK59orU2BSz0TvAha5LN9W1 QPtjo7amW/arbFyPoGlZJjiwtOCJJlZTCw==
X-Google-Smtp-Source: ABdhPJyx5nMyJn3p8blsv3aKMcj5IgxlEOpbpKsChWKwKH8To+CLSnuE4/kBRFQTaVojpx2yAgPUJw==
X-Received: by 2002:a63:496:: with SMTP id 144mr1734875pge.353.1627881017836; Sun, 01 Aug 2021 22:10:17 -0700 (PDT)
Received: from ?IPv6:2406:e003:1188:5b01:80b2:5c79:2266:e431? ([2406:e003:1188:5b01:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id b3sm10157881pfi.179.2021.08.01.22.10.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 01 Aug 2021 22:10:17 -0700 (PDT)
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, John R Levine <johnl@taugh.com>, xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com>
Date: Mon, 02 Aug 2021 17:10:12 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/1sCfm01NnR1eFlkHcA27pMCJIPU>
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 05:10:26 -0000

From a brief experiment, the xml2rfc convertor at https://xml2rfc.tools.ietf.org/experimental.html simply can't deal with the xml files at https://www.rfc-editor.org/info/rfcXXXX, right back to RFC8650.

The specific element causing the problem appears to be pn="xxx" which is like anchor only different. The published XML is littered with pn's.

Regards
   Brian

On 02-Aug-21 16:10, Martin J. Dürst wrote:
> On 2021-08-02 10:49, John R Levine 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).
> 
> Regards,   Martin.
> 
>> Regards,
>> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>> Please consider the environment before reading this e-mail. https://jl.ly
>>
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>

v2.23.0 | Report a Bug | By Email