Re: [Tools-discuss] Suppressing or eliminating warnings from xml2rfc?

Jean Mahoney <jmahoney@amsl.com> Fri, 03 March 2023 18:54 UTC

Return-Path: <jmahoney@amsl.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFC0C1516EA for <tools-discuss@ietfa.amsl.com>; Fri, 3 Mar 2023 10:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PL0LLHk2WkrW for <tools-discuss@ietfa.amsl.com>; Fri, 3 Mar 2023 10:54:13 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CD24C15152C for <tools-discuss@ietf.org>; Fri, 3 Mar 2023 10:54:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 58763424FFF4; Fri, 3 Mar 2023 10:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BT_LeD-zLXju; Fri, 3 Mar 2023 10:54:13 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 2C7FD424FFF3; Fri, 3 Mar 2023 10:54:13 -0800 (PST)
Message-ID: <3a97ec6e-2365-e11d-b9d4-39e544366cd7@amsl.com>
Date: Fri, 03 Mar 2023 12:54:12 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.7.2
Content-Language: en-US
To: Paul Hoffman <paul.hoffman@vpnc.org>, Tools Team Discussion <tools-discuss@ietf.org>
References: <D7064FBD-FA92-4BC9-AB16-1BCA4901F19D@vpnc.org>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <D7064FBD-FA92-4BC9-AB16-1BCA4901F19D@vpnc.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/ofyJJH-4-dxyRnlQj-bJH6NANt4>
Subject: Re: [Tools-discuss] Suppressing or eliminating warnings from xml2rfc?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Mar 2023 18:54:17 -0000

Hi Paul,

Converting the file to v3 will remove the warning about 
rfc2629-xhtml.ent the next time you run xml2rfc. You don't have to make 
any changes to the file before uploading it to author-tools.ietf.org to 
convert it.

However, you will need to make a few updates to the <rfc> element in the 
resulting v3 file before running xml2rfc on it again:

    o  You need to add a docName attribute that contains the new draft 
name.

    o  You also need to remove the number attribute (i.e., number="7958").

If the file you are working with is rfc7958.xml, you will also need to 
remove the consensus attribute from the <rfc> element because 
submissionType="independent".

After these updates are made, xml2rfc should be happy with your file.

Best regards,
Jean





On 3/3/23 9:51 AM, Paul Hoffman wrote:
> Greetings again. I have gotten an XML file from the RPC to use as the basis of a -bis document. When I process it with xml2rfc 3.16.0, I get a slew of warnings that I would prefer not to see:
>
> Warning: /Users/paul.hoffman/Library/Python/3.11/lib/python/site-packages/xml2rfc/templates/rfc2629-xhtml.ent is no longer needed as the special processing of non-ASCII characters has been superseded by direct support for non-ASCII characters in RFCXML.
> Warning: /Users/paul.hoffman/Library/Python/3.11/lib/python/site-packages/xml2rfc/templates/rfc2629-other.ent is no longer needed as the special processing of non-ASCII characters has been superseded by direct support for non-ASCII characters in RFCXML.
> ...repeated three more times...
>
> There doesn't seem to be a way to suppress these other than -q, which also suppresses the desired announcement at the end that the draft was written out.
>
> The file from the RPC starts with:
> <?xml version="1.0" encoding="US-ASCII"?>
> <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
> <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
> <!ENTITY rfc1034 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml">
> ...
> ]>
>
> --Paul Hoffman
>
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org - https://www.ietf.org/mailman/listinfo/tools-discuss
>