IETF Logo Mail Archive

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

Henrik Levkowetz <henrik@levkowetz.com> Tue, 29 October 2019 06:32 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 5C0F1120048 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 28 Oct 2019 23:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 tnehdbvMrFpN for <xml2rfc-dev@ietfa.amsl.com>; Mon, 28 Oct 2019 23:32:00 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [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 E8997120020 for <xml2rfc-dev@ietf.org>; Mon, 28 Oct 2019 23:31:59 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:55812 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 1iPL2s-0005AE-8w; Mon, 28 Oct 2019 23:31:58 -0700
To: Carsten Bormann <cabo@tzi.org>, Julian Reschke <julian.reschke@gmx.de>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <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> <d53ef90e-5a50-1472-a61e-12c7a417ac44@icann.org> <b19cd7de-6992-a3b5-ea23-929627018cc0@gmx.de> <019a4a58-ca92-0497-1155-303fba341241@gmx.de> <FB3B5D3A-2AFF-4ACE-BD71-D9EE2F9A4908@tzi.org>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <4911a729-648a-a6c7-e673-4dd0fc0cadac@levkowetz.com>
Date: Tue, 29 Oct 2019 07:31:49 +0100
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: <FB3B5D3A-2AFF-4ACE-BD71-D9EE2F9A4908@tzi.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Q1mIqkloDOLAVMLHT8qq7uo2bEk6AbDHL"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@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/xml2rfc-dev/WGTknszPPvDAsWgAtaJ5-S-Pgys>
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: Tue, 29 Oct 2019 06:32:01 -0000

On 2019-10-29 07:16, Carsten Bormann wrote:
> On Oct 29, 2019, at 06:50, Julian Reschke <julian.reschke@gmx.de> wrote:
>> 
>> On 22.10.2019 18:59, Julian Reschke wrote:
>>> On 18.10.2019 19:55, Paul Hoffman wrote:
>>>> On 10/18/19 10:33 AM, Sandy Ginoza wrote:
>>>>> I don’t think we'll need <br> in titles; it's sufficient to have wj,
>>>>> nbsp, and nbhy.
>>>> 
>>>> Thanks. Do you feel the same about <name>, which has similar semantics?
>>>> ...
>>> 
>>> I would think so (/me not Sandy, though).
>>> 
>>> Anyway, I think we *do* have consensus about introducing <br> in certain
>>> places where prose is allowed. It would be good to implement that so
>>> that the spec(s?) that is in AUTH48 can move forward.
>>> 
>>> We can always revisit this and add <br> in more places when the need
>>> comes up, and we have looked at alternatives.
>>> 
>>> Best regards, Julian
>> 
>> No feedback? One more week has passed, and this really looks like
>> something that should have top priority…
> 
> Feedback from whom?
> I didn’t reply to your summary because I thought we had a conclusion.

Here's what I've understood so far:

<br> generally available:

	Brian
	Miek
	Tony
	Henrik

Generally Available except maybe in title:

	Sandy

Available except in title and name:

	Julian

Limited availability (only in some named tags)

	Paul

Available in many places, but position on title unclear to me:

	Carsten


Regards,

	Henrik

v2.23.0 | Report a Bug | By Email