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

Henrik Levkowetz <henrik@levkowetz.com> Fri, 18 October 2019 17:36 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 29F9412011F; Fri, 18 Oct 2019 10:36:18 -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 wKbVRf2N1e_E; Fri, 18 Oct 2019 10:36:17 -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 01E98120118; Fri, 18 Oct 2019 10:36:17 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:51755 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 1iLWAh-0001xp-Nq; Fri, 18 Oct 2019 10:36:16 -0700
To: Carsten Bormann <cabo@tzi.org>
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> <860c663b-744f-a033-cc50-96088bb1b33c@gmx.de> <04DCBCE3-2C8C-4B03-9081-EF2B7A5C6087@tzi.org> <b096e29c-02a0-e009-621e-c1eca4712226@levkowetz.com> <4321EEBF-92C2-4405-81BD-899C0FCAC762@tzi.org> <5593c2d9-0bb4-93e9-f5d0-babf194340bf@levkowetz.com> <6BF7D165-EA48-44C1-9153-3F011058561F@tzi.org> <7088451e-745b-a31b-88fb-bce9cb48696a@levkowetz.com> <ABC71A32-09AC-4020-B2DF-A7C1AF66B106@tzi.org>
Cc: Julian Reschke <julian.reschke@gmx.de>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <1e0079b6-0cd4-4cb5-b0c7-e47ebb050b0c@levkowetz.com>
Date: Fri, 18 Oct 2019 19:36:07 +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: <ABC71A32-09AC-4020-B2DF-A7C1AF66B106@tzi.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="hfiKNBooMjpfaF72Rip1vowbKvlva4N9D"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org, julian.reschke@gmx.de, cabo@tzi.org
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/13b-GGx_fOvVBlTnd7UoW4dpK-0>
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 17:36:18 -0000

Hi Carsten,

On 2019-10-18 18:53, Carsten Bormann wrote:
> On Oct 18, 2019, at 18:05, Henrik Levkowetz <henrik@levkowetz.com>; wrote:
>> 
>> Coming back to Carsten's point about well-defined semantics, I'm not sure
>> that is the case for <sub> and <sup>.  Should that imply text stacking
>> within for instance the <sup>, or should the whole line be broken and the
>> superscript continued on the next line?  Does that even make sense?
> 
> To me this sounds like any use cases would involve math, which should be handled separately.
> 
> If we are unsure about the semantics, we should not put that nesting in.
> We can always amend the schema; we just don’t want to amend the existing instances that need to conform to any new version.
> 
> I share Julian’s curiosity about the use cases (really: intended semantics) for title/br.

I wrote about this last year.  But essentially, it's a matter of how to
break a long title; of making it possible to break a long title in at a
point that makes sense for a reader.  Two cases where the document title
is too long to display nicely, and line breaking helps/would help:

 1) https://www.ietf.org/id/draft-levkowetz-xml2rfc-v3-implementation-notes-10.html
    (or, if you prefer)
    https://www.ietf.org/id/draft-levkowetz-xml2rfc-v3-implementation-notes-10.txt

 2) In a PDF rendering received from the RPC, the title of RFC8648-to-be,
    "RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)"
    broke across lines as follows:

      RADIUS Attributes for Softwire
      Mechanisms Based on Address plus Port (A
      +P)

    which is less than perfect.  Having <br/> as a tool makes sense to me
    here too.


> The one example we can see in RFC-8668-to-be is
> 
>   <li><t>L2 Bundle Member Link Local Identifiers&br;
>   (4 * Number of L2 Bundle Member Descriptors octets)</t>
> 
> where I think we already have consensus that this should go in.

Ack.

> (And, yes, defining the entity as <br/> is a nice way to make that transition.)

Ack.

	Henrik