IETF Logo Mail Archive

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

Jean Mahoney <jmahoney@amsl.com> Thu, 19 January 2023 16:10 UTC

Return-Path: <jmahoney@amsl.com>
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 4D347C14CE47; Thu, 19 Jan 2023 08:10:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, 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 XNxlUP-s7CBs; Thu, 19 Jan 2023 08:10:26 -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 5F3C5C14CF15; Thu, 19 Jan 2023 08:10:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 50448424FFE4; Thu, 19 Jan 2023 08:10:26 -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 uQhKWP1rZbg3; Thu, 19 Jan 2023 08:10:26 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id E9AAF424B44A; Thu, 19 Jan 2023 08:10:25 -0800 (PST)
Message-ID: <53566677-148e-d945-fd8f-9c289db62036@amsl.com>
Date: Thu, 19 Jan 2023 10:10:25 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Content-Language: en-US
To: 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>
Cc: rfc-markdown@ietf.org
References: <CAD2=Z87EMetcpv66YY_b2+X1-yFy4cTpKMjPoJL=cH99c7P_Uw@mail.gmail.com> <9d719176-a4eb-7cce-e706-10325700531c@petit-huguenin.org>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <9d719176-a4eb-7cce-e706-10325700531c@petit-huguenin.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/dOxKbcN8ZhDDbRQEusuFnfr9eio>
Subject: Re: [Rfc-markdown] [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:10:28 -0000

Marc,

RFC 7997 provides guidance on the use of non-ASCII; however, xml2rfc was 
too restrictive in its enforcing of it.

Please see the announcement of RSAB's decision regarding this here:
https://mailarchive.ietf.org/arch/msg/rswg/LtZcNiVXhkG8R1XLd5pyO-LE1Xo/

This is also covered in the PR for the feature:
https://github.com/ietf-tools/xml2rfc/pull/895

Best regards,
Jean


On 1/19/23 9:41 AM, Marc Petit-Huguenin 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?
>
>> * Add editorial stream.
>> * New flag --warn-bare-unicode when set, xml2rfc warns about bare
>> Unicode in the <t> elements. By default, this is set to False.
>>
>> Report any issues on https://github.com/ietf-tools/xml2rfc/issues
>>
>
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org - https://www.ietf.org/mailman/listinfo/tools-discuss

v2.23.0 | Report a Bug | By Email