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

Sandy Ginoza <sginoza@amsl.com> Fri, 04 October 2019 19:42 UTC

Return-Path: <sginoza@amsl.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 9CC3E12003E; Fri, 4 Oct 2019 12:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 Vn_AiF4by-ho; Fri, 4 Oct 2019 12:42:45 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F6D8120025; Fri, 4 Oct 2019 12:42:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 18EC4203422; Fri, 4 Oct 2019 12:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVfpgNlxv6tL; Fri, 4 Oct 2019 12:41:58 -0700 (PDT)
Received: from [IPv6:2605:e000:1524:de:7c43:ae21:e098:86ba] (unknown [IPv6:2605:e000:1524:de:7c43:ae21:e098:86ba]) by c8a.amsl.com (Postfix) with ESMTPSA id B129220341D; Fri, 4 Oct 2019 12:41:58 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <B15F7AF0-F5A0-401A-9F6E-F7E0E466B6A7@amsl.com>
Date: Fri, 4 Oct 2019 12:42:44 -0700
Cc: Henrik Levkowetz <henrik@levkowetz.com>, "HANSEN, TONY L" <tony@att.com>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BF4598E-EDB7-49D6-8070-BBE0AA9F24F9@amsl.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>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/kFvB2WU1zkGYqQiBSCmtTYztA34>
Subject: Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] <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, 04 Oct 2019 19:42:46 -0000

Just an additional point on this one.  Henrik has already suggested differently handling — looks like we haven’t implemented yet.  This one is included to show where a <br> could have been useful instead of looking for creative ways to workaround not having it.  


> a) This issue has come up quite a bit when we were trying to update lists/sublists where the authors want no whitespace between the indented items (no bullets; just a line break).  For example, RFC 8668 (v3 files not yet posted) contains the following in the v2 text:
> 
>      L2 Bundle Member Attributes
> 
>         Type:  25
>         Length:  Number of octets to follow
> 
>      Parent L3 Neighbor Descriptor
> 
>         L3 Neighbor System ID + pseudonode ID (7 octets)
>         Flags: 1-octet field of the following flags:
> 
> We were able to replicate this spacing with the following XML, which seems bad because we have empty <dd/> to get the right spacing.  If there is a better way to do this, please let us know. 
> 
> <ul empty="true">
> <li>
> <dl spacing="compact"><dt>L3 Neighbor System ID + pseudonode ID (7 octets)               
> </dt><dd></dd>
> <dt>Flags: 1-octet field of the following flags:</dt><dd></dd>
> </dl>