Re: [xml2rfc] [Tools-discuss] New xml2rfc release: v3.16.0

Carsten Bormann <cabo@tzi.org> Thu, 19 January 2023 17:18 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 12CAEC14CEE4; Thu, 19 Jan 2023 09:18:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 en3eDJtm-7CG; Thu, 19 Jan 2023 09:18:43 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (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 B68F6C14EB17; Thu, 19 Jan 2023 09:18:39 -0800 (PST)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4NyTqc0B6FzDCbL; Thu, 19 Jan 2023 18:18:36 +0100 (CET)
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: <53566677-148e-d945-fd8f-9c289db62036@amsl.com>
Date: Thu, 19 Jan 2023 18:18:35 +0100
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, Kesara Rathnayake <kesara@staff.ietf.org>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org, tools-discuss <tools-discuss@ietf.org>, rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 695841515.398162-8c61b919f3cf0c5af0831bcf05c61b08
Content-Transfer-Encoding: quoted-printable
Message-Id: <63391716-EC1F-4EAE-BE77-A8DE402D84B3@tzi.org>
References: <CAD2=Z87EMetcpv66YY_b2+X1-yFy4cTpKMjPoJL=cH99c7P_Uw@mail.gmail.com> <9d719176-a4eb-7cce-e706-10325700531c@petit-huguenin.org> <53566677-148e-d945-fd8f-9c289db62036@amsl.com>
To: Jean Mahoney <jmahoney@amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/AnXEM_SpBycqV04ic6zhVIQs2pA>
Subject: Re: [xml2rfc] [Tools-discuss] New xml2rfc release: v3.16.0
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 19 Jan 2023 17:18:46 -0000

On 2023-01-19, at 17:10, Jean Mahoney <jmahoney@amsl.com> wrote:
> 
> RFC 7997 provides guidance on the use of non-ASCII; however, xml2rfc was too restrictive in its enforcing of it.

Note that while RFC 7997 mandates the mention of code points for characters that go into the protocol, it does not mandate the use of <u.  (It cannot have mandated that, as <u wasn’t invented yet.)  Requiring the use of <u to fulfill the requirement of RFC 7997 clearly was overstepping the remit of the tool that is xml2rfc.

Grüße, Carsten