Re: [xml2rfc-dev] Warning messages - How to address?
Jay Daley <exec-director@ietf.org> Wed, 02 February 2022 19:15 UTC
Return-Path: <exec-director@ietf.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B9D3A1C8E; Wed, 2 Feb 2022 11:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 1Bz2HKIikCBX; Wed, 2 Feb 2022 11:15:20 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CEB43A1C8B; Wed, 2 Feb 2022 11:15:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id E935E4113627; Wed, 2 Feb 2022 11:15:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnC6tG33zHih; Wed, 2 Feb 2022 11:15:19 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 3EC8D4113625; Wed, 2 Feb 2022 11:15:19 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <0567AF8D-9EC1-4DF8-B5B8-66B967C59B2E@gmail.com>
Date: Thu, 03 Feb 2022 08:15:15 +1300
Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D79500F0-3BB2-480E-901F-E15F385C0C7C@ietf.org>
References: <0567AF8D-9EC1-4DF8-B5B8-66B967C59B2E@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/UGXzxqJDwymvODvtp7HRkU31GtA>
Subject: Re: [xml2rfc-dev] Warning messages - How to address?
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2022 19:15:25 -0000
Hi Mahesh The tl;dr is that you do not need the DOCTYPE statement that includes a .ent file. Read https://authors.ietf.org/en/templates-and-schemas#character-entities for a fuller explanation. Jay > On 3/02/2022, at 7:38 AM, Mahesh Jethanandani <mjethanandani@gmail.com> wrote: > > I am seeing the following warning messages using the latest version of xml2rfc (3.12.1). Do not know how to address them. Can anyone help? Thanks. > > % xml2rfc draft-ietf-netconf-https-notif-09.xml -o draft-ietf-netconf-https-notif-09.txt --text > Warning: /usr/local/lib/python3.8/dist-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: /usr/local/lib/python3.8/dist-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. > Warning: /usr/local/lib/python3.8/dist-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: /usr/local/lib/python3.8/dist-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. > Warning: /usr/local/lib/python3.8/dist-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: /usr/local/lib/python3.8/dist-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. > Warning: /usr/local/lib/python3.8/dist-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: /usr/local/lib/python3.8/dist-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. > > Mahesh Jethanandani > mjethanandani@gmail.com > > > > > > > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev -- Jay Daley IETF Executive Director exec-director@ietf.org
- [xml2rfc-dev] Warning messages - How to address? Mahesh Jethanandani
- Re: [xml2rfc-dev] Warning messages - How to addre… Jay Daley
- Re: [xml2rfc-dev] Warning messages - How to addre… Lars Eggert