Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New xml2rfc release: v2.25.0

Julian Reschke <> Tue, 27 August 2019 05:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C4DBC120F18; Mon, 26 Aug 2019 22:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vR7uT9rloKQT; Mon, 26 Aug 2019 22:48:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 15297120823; Mon, 26 Aug 2019 22:48:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=badeba3b8450; t=1566884916; bh=OLUaWJK/LqxAytsYHw3IHn+zcsVGFvwOWJm4MNMCYz8=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=jCpTNSwDstTmDmepVAFWcygfFkGMRZxIIasleCu7T9xOKi+g9aOPJx7pehU/NpOJU hcZMIw/DZZhpZ/1vx+dHByKOirGR/JFx/eOKMOdEDYPX9OX0HPYuy4k0CRVgyCuCup Uun4/IGSFNGsJZEkGdsgtvtByum+mbfWcEBVUS6o=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [] ([]) by (mrgmx005 []) with ESMTPSA (Nemesis) id 1MhU5R-1ignIt1wqR-00ecbe; Tue, 27 Aug 2019 07:48:36 +0200
To: Henrik Levkowetz <>, Dave Lawrence <>,,,
References: <> <> <> <> <> <> <>
From: Julian Reschke <>
Message-ID: <>
Date: Tue, 27 Aug 2019 07:48:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:gPfqQwut2/N3EIU9Lppzf5n0y+xNF7Rn/XWvgKx6hKW6XsraFXK bDU2FjV2oflr/OpSFFojZSaHiSpbiAvTAnGQ/rcm1v7hzoIWl+lzw/3AHehJKyX6wd+pbT7 8T+Rulw+vYWw+Ioo/xEWt1h1bVzf5NtvK6sMRqCINqvJHjFU+UbL8uGVjGwpeWUCUQWFs0G pyDZVYrMreYuJIZhppMJA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:sP2J9TUD9vs=:DtwBiWCqwPVnjp/opLTDWe dbls24pwot69oA7xtc8ryQmHh3fZM7JJJyYLqBwc2lOrXUal9wwJMIWwf0BvzfpnMKX30Hllb 1zSJrGVohQ68Clye/7/+e/3xwY89oPGVVLirIxH0ni529tQWwkGcCJCUsxscvrXnFJbiZts63 Bq6p16kP4yWTPsLyBjYyrwFhGrxDygqq4DIKCUJ5TfABFGtEAN3I4EHmtp+5piXbkrgbUyXgA hwfgOwFSqqTgsludK26iJu8ACDUxdPnIjUMxgYGsaHgV/Y5jJL4mDvy39SzGEDsGOMlGooYFW 939C++lEoKJ4zt6m1xchLt3G1iI8lDxAVAE/jCwIO1Y3ubqEWxHMK9TGfPe3hANNlp+gWLOT9 c+WI4xdg4ediy3Uu7Q1xIVKgT1BLBGRsC50wwIdamqPGrrwUTHMQQsiPr/sze5q3Bh5GGl6sU XRE75JudDI7ZFVOY8aJXEFSBnzSSxRNsQCyNf+HeoJVE1EDH1puvnyS4uTewv3/4sNDaP8PP5 4IZjC9+xZdwLOTST7m0sNvmMsNqIzNKfERJTiKp7mp5IT45n/zj6BNDS0G3b/Sj64o0NKAlc4 h08Xxosdtzd2CpXH1z0G4wjt16deJGcgH5cqMToarO7proi3SuWrb4cgEBT+QsdsaUtwt+Dgx 9Yt8Zt+Fp4mUrS9P6WvG2RiKFvjBF524NHkreuAVhKb7UED5Sb8LkRjaOAnXf7mgJUcBx9z9F a6QZ5r6TgZOFcwRPXg3QMf8az7Luuf4/HbH88ZqJVz11PtINvCiVbRJ/NGwH5Sz87m2PiJvsb hCMu9mb/VHGHhDAuqEuk+MeKP2V5ZmxFL1CJXcXBZOpaROp5wFxne8iRu6+P63Y+M9vDuruup Nhc3rGS5WUxPcgME6Rb/iIPEdioc//GobpHtwnd3bqQxem4ExyuMWUv1xjywgqoL/lYJZVnfW gZDvdwT3XiH2ClC42AG8iKvwFjxgi88OOUNaOtndsgWgwoJjyIF5ItmEFbuZdJmQcrBkSpXs4 XNGHuMqdy02m+V10t3ZA7EJrhHwPfYeKP3/boZU28hotZqEEYD/NL8u1gUQ3yPjuRG9qr5yQh UG+CognB3D1zPfDpE0WlaQOegU6DqkPRC0ozNdTD3+/sSEPeXN3lZ5YjxXGr+cWW8pLQzhBha 3I5C1e49DfCQpW27kk1fIQPAOLBTgFv/ebkXLLmyLq7souvg==
Archived-At: <>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New xml2rfc release: v2.25.0
X-Mailman-Version: 2.1.29
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 Aug 2019 05:48:53 -0000

On 27.08.2019 01:46, Henrik Levkowetz wrote:
> Hi Dave,
> On 2019-08-27 01:06, Dave Lawrence wrote:
>> Julian Reschke writes:
>>> If the sole reason for this change is to avoid breaking up MUST_NOT (and
>>> friends), why not hard-wire that into the renderers (for HTML, I believe
>>> it could be done with CSS...)?
>> And I readily admit I might have missed a memo, but if that is the
>> sole reason then how did we arrive at the conclusion that they needed
>> to be inseparable?
> They don't.  There's no such rule that I know of, and I don't think there
> should be one.
> But if an RPC editor decides to make it so in some cases, why should xml2rfc
> get in the way and issue an inappropriate warning about unrecognised keywords?

It would be good to better understand the requirement. In particular I'd
like to understand why this needs to happen on a case-by-case basis. It
sounds as if historic requirements (line breaking in plain text) leak
back into the canonical source file.

> No reason to do so that I can see.  Which is why I made xml2rfc recognize
> both "MUST NOT" and "MUST&nbsp;NOT" (and "MUST\tNOT", and "MUST\nNOT", and
> some others) as a BCP 14 key word.

What about other non-ASCII whitespace characters?

Best regards, Julian