IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@icann.org> Thu, 19 January 2023 16:12 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F08B7C14CF1D; Thu, 19 Jan 2023 08:12:11 -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 u_ZTRAHxpRg5; Thu, 19 Jan 2023 08:12:06 -0800 (PST)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 C34B7C14CF15; Thu, 19 Jan 2023 08:12:06 -0800 (PST)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa2.lax.icann.org (8.17.1.19/8.17.1.19) with ESMTPS id 30JGC5B8008224 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 19 Jan 2023 16:12:05 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.20; Thu, 19 Jan 2023 08:12:03 -0800
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.1118.020; Thu, 19 Jan 2023 08:12:03 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
CC: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, tools-discuss <tools-discuss@ietf.org>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>
Thread-Topic: [Ext] [Rfc-markdown] [Tools-discuss] New xml2rfc release: v3.16.0
Thread-Index: AQHZLCDEfMi3Q4BN1UanbTgqW5fzrA==
Date: Thu, 19 Jan 2023 16:12:03 +0000
Message-ID: <4925CBA6-6CF4-40F7-9CF5-E55D2F9CD438@icann.org>
References: <CAD2=Z87EMetcpv66YY_b2+X1-yFy4cTpKMjPoJL=cH99c7P_Uw@mail.gmail.com> <9d719176-a4eb-7cce-e706-10325700531c@petit-huguenin.org>
In-Reply-To: <9d719176-a4eb-7cce-e706-10325700531c@petit-huguenin.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F091BAA2FF47844E8BE7D94EB1EF2EFD@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.930,Hydra:6.0.562,FMLib:17.11.122.1 definitions=2023-01-19_09,2023-01-19_01,2022-06-22_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/q2kvbeXVCUVQMv6-X8OPfJV4gbk>
Subject: Re: [Rfc-markdown] [Ext] [Tools-discuss] New xml2rfc release: v3.16.0
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2023 16:12:12 -0000

On Jan 19, 2023, at 7:41 AM, Marc Petit-Huguenin <marc@petit-huguenin.org> wrote:
> 
> On 1/18/23 14:09, Kesara Rathnayake wrote:
>> See https://github.com/ietf-tools/xml2rfc/releases/tag/v3.16.0 for
>> release details.
>> 
>> New changes include,
>> * Permit non-ASCII within <t> without the use of <u>.
> 
> Isn't an unconditional use of non-ASCII a violation of RFC 7997?

It should not be, but it would be good to hear which parts of 7997 you think would be violated so we can update the RFC.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email