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

Henrik Levkowetz <henrik@levkowetz.com> Fri, 18 October 2019 18:34 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 117D51208E5 for <xml2rfc-dev@ietfa.amsl.com>; Fri, 18 Oct 2019 11:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level:
X-Spam-Status: No, score=-1.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] 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 yAZA4y0k9kNB for <xml2rfc-dev@ietfa.amsl.com>; Fri, 18 Oct 2019 11:34:11 -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 132A01208C0 for <xml2rfc-dev@ietf.org>; Fri, 18 Oct 2019 11:34:11 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:51932 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 1iLX4k-0002Ta-8W; Fri, 18 Oct 2019 11:34:10 -0700
To: Paul Hoffman <paul.hoffman@icann.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <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> <efb58534-8112-2303-1967-536daae9ff51@gmx.de> <34FFD9FB-7D0A-4BEE-9BAD-AFBD7F883CE6@amsl.com> <b43d1d27-b193-795b-c3c3-7b652039fdd3@levkowetz.com> <755cea57-d3a8-cfd8-a621-69d931e90991@icann.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <530981d3-11d8-63c7-3bc4-aad5b52938ab@levkowetz.com>
Date: Fri, 18 Oct 2019 20:34:02 +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: <755cea57-d3a8-cfd8-a621-69d931e90991@icann.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="2Obk3FJjdC400An3s7KBPgEte760sMrIN"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, paul.hoffman@icann.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/xml2rfc-dev/m0LE1ouTIi3TdGGul_HayhouUqA>
Subject: Re: [xml2rfc-dev] [Ext] Re: [Rfc-markdown] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2019 18:34:12 -0000

Hi Paul,

On 2019-10-18 20:29, Paul Hoffman wrote:
> On 10/18/19 11:12 AM, Henrik Levkowetz wrote:
>> So, how would you handle the first of my two examples in an earlier message
>> in this thread:  The title of my implementation notes draft, which requires
>> more than one line both in text, html and pdf rendering:
>> 
>>                       Implementation notes for RFC7991,
>>                      "The 'xml2rfc' Version 3 Vocabulary"
> 
> This question presupposes that where a title is broken in a
> particular rendering is important. RFCs 7792, 7794, and 7795 did not
> indicate any such importance in their discussion of titles. In
> particular, for the HTML rendering that most people focused on in the
> discussion that led to the v3 format, line breaks are explicitly
> unimportant because the rendering might be on a narrow screen. It
> sounds like this issue is being brought up despite the text in the
> relevant RFCs.

Yes, well, I'm bringing this issue up because I ran smack into it with
the title of my implementation notes draft.  In real life, I think there
are cases where indicating a particular break point makes sense.  To me,
it is that simple.


	Henrik