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

Henrik Levkowetz <henrik@levkowetz.com> Tue, 08 October 2019 16:17 UTC

Return-Path: <henrik@levkowetz.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 4A91F120168; Tue, 8 Oct 2019 09:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.095
X-Spam-Level:
X-Spam-Status: No, score=-1.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 1j5zo41Nw2EU; Tue, 8 Oct 2019 09:17:36 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7577C1200B9; Tue, 8 Oct 2019 09:17:36 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:49286 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iHsB2-00006e-D4; Tue, 08 Oct 2019 09:17:34 -0700
To: Sandy Ginoza <sginoza@amsl.com>, "HANSEN, TONY L" <tony@att.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>
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>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <c88388ff-84ae-c5f5-e093-e9aee77da3d6@levkowetz.com>
Date: Tue, 8 Oct 2019 18:17:24 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <07DBAE10-D1FA-45C4-B7A2-321B265CA302@amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9XTVAtk7E0aHMH0r96cli0KIb3iLTXa2O"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: brian.e.carpenter@gmail.com, xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org, tony@att.com, sginoza@amsl.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/qLbRpm5nv8-O9D1msEeUBq3WAjI>
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: Tue, 08 Oct 2019 16:17:37 -0000

On 2019-10-08 17:21, Sandy Ginoza wrote:
> Hi Tony,
> 
>> On Oct 6, 2019, at 7:20 PM, HANSEN, TONY L <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>.


Ok, I then propose that we permit <br> in body text, including lists and
tables, and in document and section titles.  More specifically, I propose to
permit <br> as a child element of these elements:

   blockquote
   dd
   dt
   em
   li
   name
   strong
   t
   td
   th
   title
   tt

(Should <sub> and <sup> be in that list?  If we compare with the places where
for instance <bcp14> is permitted, the answer would be 'yes'; but I'm not
sure it's the right thing to do.)


	Henrik