IETF Logo Mail Archive

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

Marc Petit-Huguenin <marc@petit-huguenin.org> Thu, 19 January 2023 17:25 UTC

Return-Path: <marc@petit-huguenin.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 CFF87C14CF1C; Thu, 19 Jan 2023 09:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 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_HELO_FAIL=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 aSxfWO-dIvvN; Thu, 19 Jan 2023 09:25:23 -0800 (PST)
Received: from implementers.org (implementers.org [92.243.22.217]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F3E1C14CF0D; Thu, 19 Jan 2023 09:25:23 -0800 (PST)
Received: from [IPV6:2601:204:e37f:a6af:d250:99ff:fedf:93cf] (unknown [IPv6:2601:204:e37f:a6af:d250:99ff:fedf:93cf]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id ED57BAE232; Thu, 19 Jan 2023 18:25:20 +0100 (CET)
Message-ID: <91db90d9-263b-3a32-bdfb-906f3ffbb849@petit-huguenin.org>
Date: Thu, 19 Jan 2023 09:25:18 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0
Content-Language: en-US
To: Jean Mahoney <jmahoney@amsl.com>, 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> <53566677-148e-d945-fd8f-9c289db62036@amsl.com>
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
In-Reply-To: <53566677-148e-d945-fd8f-9c289db62036@amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------RyW0baCQn1FpukQQthIWdyef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/mCeXfrvdmoRmVkOatuy8S3CF6dY>
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 17:25:27 -0000

Hi Jean,

Responding in the order that I received the responses.

See my previous response to Jay and below

On 1/19/23 08:10, Jean Mahoney wrote:
> 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/

Obviously I think that the RSAB is wrong here, and I see that as a tactic to go around RFC 7997.  At a very minimum an RFC 7991 bis should be published, so I can scream at it.

> 
> 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

-- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug

v2.23.0 | Report a Bug | By Email