IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Thu, 19 January 2023 17:55 UTC

Return-Path: <julian.reschke@gmx.de>
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 920D7C151546 for <rfc-markdown@ietfa.amsl.com>; Thu, 19 Jan 2023 09:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.de
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 tpRY0wdKc4TE for <rfc-markdown@ietfa.amsl.com>; Thu, 19 Jan 2023 09:55:09 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26AEEC14F738 for <rfc-markdown@ietf.org>; Thu, 19 Jan 2023 09:54:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1674150865; bh=FI2HZmpNy04WlzuS405jTi5GBa+4Exk33S68nnkl1yg=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=J7sV0rDHqrhfI1s9yAL+qgu2zXgZilpQIuCgEWWKbSoXcmTDbBc72KKbz/zQGh5J7 8GOqRGfgXYt/gsSG2SLuM+nXJHsqeHbQNrUfnqsZGaheeaYRdLXzjYfsZO7ch3g4ci bipgumsjK5JirtRdSYMPNzFWITH2CMvHRIidNKliGca5p0SYP/cdNhFDBYhX8Ubjp0 nSQLdZfVnZMMrFCd3kBuuIrqF0+SSORH0btiynNVHGwgRze/D0gaom6v6zjtgh4pXU 0uvAtimg4CO+WlKa+rjAUbppLvESnwPLE7wSi4Vqp3bQBoBUdmta6n0TvTYvm0ui9C BYQtsF/auMrbQ==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from [192.168.178.179] ([217.251.129.102]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MjS9C-1oqQ710Cd8-00kx2w for <rfc-markdown@ietf.org>; Thu, 19 Jan 2023 18:54:25 +0100
Message-ID: <914d328b-92d8-156b-295a-5b18e730254d@gmx.de>
Date: Thu, 19 Jan 2023 18:54:24 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Content-Language: en-US
To: 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> <63391716-EC1F-4EAE-BE77-A8DE402D84B3@tzi.org> <bed83f40-08f2-e3da-702a-7bcbc83c3fe5@petit-huguenin.org>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <bed83f40-08f2-e3da-702a-7bcbc83c3fe5@petit-huguenin.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:8oaqimIFetsD2ZrngaV9kXdX8GK5ygJBf3cyyLzmqtKLvA5GU8x jH9PA9jn5J8MnhVWyQtXOyxurqkzBZGl68NA/R+Tx1lMqEVVa7Y3jvFNjbOHrdM2MQVstwM OkQ/48sRQKRMCkJCK92Gsz5nR6jhYLwQz3OmYb8Qvq7qRnZ46AwjF2nORbqvteCBnFoc75J RgujwUrqAq5KUw10EQynA==
UI-OutboundReport: notjunk:1;M01:P0:s4k6Qn6ZDsw=;RcRkAXuJ0pl/l9cd0pYZ6VbgYpZ Vim8VHYqWV3jRHoOXrX1DgY8Hg6vGwYL345OWxfY9u1FTZMnW1sS7zQ0L0ycyBC1GZ1B6nc5M eDbi9Ei7h93atvnAQGWa+XZZY+RBqiPxfPc6YmqMuY0NJIoI1D4+T9XjfoCwuS3v+DwIiwByt oF2UjNO+QXGZfnDoPH6ZHXorHZjSMvDGcB6XbgS1exmHEGrtg8J6X/DeUg4igk/27nFGycU7F xmWKvHncPvKmP5Mxa70NpZPxYfCj3qF95c5EGoL+r5pskzzwELHrKpGS/2wKFGqMFvfNiMx+Z LQHUGv51nZu7OjT0lmiWH2OSJOft7bWuylAH+9yLpV3fZsuw+Im6U6TWjFmUtlx5algcfgrl1 Z2Cs3IZqQjGTeu201mrWsp/bZaQijwtZbh82WESiKbftXGUILL4AyowCldjm9CrMqAqYJpO3o lq94RVJyZRpM+MtSTZwqgac9NX9Fb/rn9akxC/oIkwkiWGMOzG57WgS47sjeEGG/U1qcKQPrD Yjqph+AD5k+ZgDIz4Rxyi7mep6YkZ84zV5FGjsL6fPL4xTI+AIIrQjdPOELpRx+Ne85uqAYeK UhwWKYc+UNh4f2tGTUq6xrYykcc4tkb/k5OAQSqjScXiq/FxV6ijWRm/xenzQ8QENvEvirP0e XjMuAHiJwsoLLdujsqTtOSA5Bo0S0uHHrT0eFvSsihxF6K+H/jxj+nRhcz6N98Xh0y1c2j2Gc 2rXltufhbXZw00VF6ZbIDWuSGnydVg9HnW29pL2Mwl7UsSYI8AbPZx97hhK7OhFB9tkCMcRbK 4OKcqkJOr4CQnePza0ekFdCFEmHdkaFY700I31DErFTIsYVsiVlMwU7R9/jY9Q2dJJMHGLk6o ggnPdTEbF6YaNNC2Xspd4yqhj6bz9QD+vi9wcEDxhfJVCO3kUHuTD7CBBviHk2hi6VcByBRtO yMRuxr8Xnagj5Stzrw9svbhke78=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/ei9K0-KVa447wLIh45xIfrypDo8>
Subject: Re: [Rfc-markdown] [xml2rfc] [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:55:13 -0000

On 19.01.2023 18:31, Marc Petit-Huguenin wrote:
> On 1/19/23 09:18, Carsten Bormann wrote:
>> 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.
>
> Yes it was, although it was the right idea, which was to update the xml2rfc language to be able to enforce all the exceptions listed in RFC 7997.

Which lead to other strange workaround such as to allow <author> in
prose, in order to get the non-ASCII names supported.

Best regards, Julian

v2.23.0 | Report a Bug | By Email