Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0

Julian Reschke <julian.reschke@gmx.de> Fri, 18 October 2019 10:37 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 C59B4120A1A; Fri, 18 Oct 2019 03:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEG8gb0de2sH; Fri, 18 Oct 2019 03:37:02 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D855E120B73; Fri, 18 Oct 2019 03:37:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1571395013; bh=PIulYIFNBaxXIOoJx5GI85SVxsnYoSQZbw9rhlyFqXo=; h=X-UI-Sender-Class:Subject:From:To:Cc:References:Date:In-Reply-To; b=SyD1evxifojonYkGex1qhot2d+LfjtChFlON1gKgkuQLnSt/Al5/K5NUEBB8oXZVD 9kCBHObny8Metw2ZqiICutSb8yzDMS07nGyWqcb+5NdDklS9zsZycAf/QOD3CofRx3 9lSI7+pLHKfkzMk1WHRdKE7zWIAWCevv0TxL1S9Y=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Md6Mj-1hmLvL40At-00aH6T; Fri, 18 Oct 2019 12:36:53 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: Sandy Ginoza <sginoza@amsl.com>, "HANSEN, TONY L" <tony@att.com>
Cc: "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <8304e61d-c550-91ea-9e23-eef2cd31240b@gmx.de> <A3513970-EEB0-4DBD-9E6F-A87EBFAF886D@att.com> <de4feaff-8f71-cd38-545c-2d848749251b@levkowetz.com> <f00a671a-6fe4-f5ae-2582-0b78ffa1c256@gmx.de> <1f18382c-d830-b887-f5d3-3f376ae4fdd7@gmx.de> <B15F7AF0-F5A0-401A-9F6E-F7E0E466B6A7@amsl.com> <f4f1b7ba-127a-fbfa-531b-eeff03814281@gmx.de> <71bc8d39-d06c-d900-cc8e-04a48218d75f@gmail.com> <0905DADC-E9D5-47A7-B610-F8A62686D2BD@att.com> <07DBAE10-D1FA-45C4-B7A2-321B265CA302@amsl.com> <694c9244-98ae-1e64-39ef-8756d48b36ef@gmx.de>
Message-ID: <860c663b-744f-a033-cc50-96088bb1b33c@gmx.de>
Date: Fri, 18 Oct 2019 12:36:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <694c9244-98ae-1e64-39ef-8756d48b36ef@gmx.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:t0LwY0+tMiz3lqnjHDQQsDDmyhjmRxKnqZISwBiGa9NAIja75dt 2x0Jazb4eUzDyK5456JFXjPjJDLoXctddi7g3LFH0Gp1rYYxnig6boBcx19N/QjCCuMEhR/ eZL5qNvKsh5h/etmMdH4007YUeG0wN9ixUvoFNW5af7T5rLg5zY8yFLT2nvvfYIYGd8i24Y QVIjQ/GyszIkVSGHWAVEw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:9NMD2+J/oWI=:JsEM8A+Zfc+OJ/horDgdMz Gsw/AoU/LqaPnXrGLg9+hjfSPG+MoLPXsSFnBAhojquGTmFcN8FAKkbJslKYRelICNvQXQh4l MVCTtctPaU9ORm4SuMw/9WvH1f1TZ3kYJea5TGETJR64eAn5PbCNXrkb3TKvocWeUO+JIlPuC TmjddhfopFieHdNQAgaLylfpRorOCV3Iyk1T3COumUgH7/GlfeG1XeU00sCJHlw2U0LyDbGM8 qrPEZoO+cC2/FWtjglKwjeoZZsQabHZLeg7tSE8qKe/LysDqZPcuyCjiNunHOxD8pdODSYssz QfYK2A3wdq51jNxL061oF3tibbniQ1gQHFECbg9to5pE8AUqWN326qzpj5gnwQfvlFvS22c9/ A9yiczk7v19hDN/yIU691SKbAMaMF7fYDtt1Is9nhT/4EKOD/3kugisPPDuxdyd7N9jamXTCH uRB9TCRMgRzO/O2gm4UDtovF0pFaBBixH+6ujfQrQa1QJQrVPBJC+0DFxcV6+7svEfR4OHpM7 YP82xQzUbknFkuuZWfYt5wezit8WtrdeEohyVUBHbf6IHRcZDADX531kMKh1Z3GlX5e6nDZzN VCJN+1LsATzH/6lOUJTjx0W0v66uHIzSHdmFvYkXMAmG+Ezl7tmz0WMeKdKnqkKCneA1U0l98 rs9PmgWVnrbTQ/aIX546uThuTV5LW87TPG2PN4gwyt7m/CL3vSFK+vyq9QEjTrGTsM5QpaXZC mhjL0+ErxRUwmFpVVlN/CHmQxheAT2tARQ/7XQoitxZqBpbnP0B2lnanTyWP+ek5BXNpp/JNo z7sXSIe6QrLcMDV56V6SgYmxmQWIk2EIhF2FWsaRQYDJvOQXB/KQA7mNf8ehIcAo+eKDjkRr+ KeXtD8cQhXVdiQxEM/MNmDQLe2UtKClAtPLQSyt7dpdQsQXRzgHspLadHmyHYiep3Sz/zaIh2 gelo8uUrzLTYxZwklJaNiQh51XEQIPjtoykbe+1MCHdnQi2dcjDfMG3og7FaYn/v/LD3p1j+R MhkmdW/qMYF1XbEdtgmNxOyXbr7RRqMPPcU0Nho0fvOXoibdS1n1VduTNLrrnzem1UOuBKhoc PHi0TTs1au89r/gAk3iTSEl5pB3FTRHjyczcXA0mjkqjvjHz5934WGrqbhAawNR2UR08P/ucM bt4W2s+jBvgbbEW7JQRNXt0S8Zrp5pS0zz5US+eEyWWYF5xs2D30uKl7lIRSZYnsjYeqUkAqc pRx+rEacyAUp2q1wb/ikCtzooZmwINXOTSjb2wtGkopob54+GrtS3gWpAn7A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/CGLy0__LupvxpqjRqVrdIu24Jss>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0
X-BeenThere: rfc-markdown@ietf.org
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." <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: Fri, 18 Oct 2019 10:37:05 -0000

On 16.10.2019 20:01, Julian Reschke wrote:
> On 08.10.2019 17:21, Sandy Ginoza wrote:
>> Hi Tony,
>>
>>> On Oct 6, 2019, at 7:20 PM, HANSEN, TONY L <tony@att.com
>>> <mailto:tony@att.com>> wrote:
>>>
>>> Sandy, does the RPC feel that the ability to add a line break is needed?
>>
>> Yes, the RPC would appreciate being able to use <br>.
>> ...
>
> Just checking: absent <br/>, are you planning to use the Unicode escape
> anytime soon? That would be a problem for the canonical XML, if we
> decide to revert this change.
> ...

I note that there is one XML in AUTH48 using this (RFC 8668), so this
really is a bit pressing.

Best regards, Julian