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 19:05 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 EBE081208B3; Fri, 18 Oct 2019 12:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 uPhCbxS9Ve9G; Fri, 18 Oct 2019 12:05:06 -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 11C82120811; Fri, 18 Oct 2019 12:05:06 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:52027 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 1iLXYe-0007sm-QF; Fri, 18 Oct 2019 12:05:05 -0700
To: Carsten Bormann <cabo@tzi.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <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> <1e0079b6-0cd4-4cb5-b0c7-e47ebb050b0c@levkowetz.com> <773D9A93-5E06-4A39-B374-C291DF34A759@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: <5523fb25-48b1-c2e5-aa0e-5e7a61593edd@levkowetz.com>
Date: Fri, 18 Oct 2019 21:04:56 +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: <773D9A93-5E06-4A39-B374-C291DF34A759@tzi.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="b9Tpve0rABE4nCVR71odO9FXxu39Dik4E"
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/8rFlkAyFnGpILJaRp611Ior2N00>
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 19:05:07 -0000

Hi Carsten,

On 2019-10-18 20:51, Carsten Bormann wrote:
> On Oct 18, 2019, at 19:36, Henrik Levkowetz <henrik@levkowetz.com>; wrote:
>> 
>> 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 problem with <br/> here is that this really is conditional on a specific line length.

Yes, of course.

> My screen does not have a problem with
> 
>   RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)
>
> (Not sure you can see this, but this is all on one line.)

Sure, in this email, yes.  But there are width limitations with both our
HMTL rendering stylesheet and its print version (for PDF).

> Binding things together more tightly works better here than providing fixed
> places for breaking things apart.

Yes, this is right in some cases -- in others, not.  Eventually, I added
support for WORD JOINER, in order to make tighter binding possible explicitly
for the case above.  But please, if you're going to analyse this example,
also do the same for my first example.

> Line breaking in titles is sometimes weird when the original form is
> multiple semantically separate lines and one wants a form that fits
> on one line. Typically, dashes are added, so
> 
>       Quantities and units
>       Part 13: Information science and technology
> 
> becomes
> 
>       Quantities and units – Part 13: Information science and technology
> 
> Breaking this up again might lead to
> 
>       Quantities and units –
>       Part 13: Information science and technology
> 
> Which is OK but not really what is wanted.

So in a medium that does not permit that line to be shown full width,
would you prefer to not provide a break point, leading to for instance

	Quantities and units – Part
	13: Information science and
	technology

or

	Quantities and units –
	Part 13: Information science
	and technology

?

If you bind every word after the dash tightly to the following words,
then you'll get a line that is force broken in a middle of a word or
alternatively extends past the display width.  If you can indicate a
break point after the dash, the following line can be broken at a good
point.

In particular in the PDF and text output cases, we _do_ have width
limitations.  With the current style sheet, in HTML too, but the
title lines there are a bit longer.

> (Are document titles poetry?)

Maybe some of them are :-)


	Henrik