IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Tue, 29 October 2019 06:16 UTC

Return-Path: <cabo@tzi.org>
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 7AB9C1200BA for <xml2rfc-dev@ietfa.amsl.com>; Mon, 28 Oct 2019 23:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 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, 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 7AgaeboR1o-g for <xml2rfc-dev@ietfa.amsl.com>; Mon, 28 Oct 2019 23:16:24 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E63FF120013 for <xml2rfc-dev@ietf.org>; Mon, 28 Oct 2019 23:16:23 -0700 (PDT)
Received: from [192.168.217.110] (p548DCA87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 472Lv92FgYz100L; Tue, 29 Oct 2019 07:16:21 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <019a4a58-ca92-0497-1155-303fba341241@gmx.de>
Date: Tue, 29 Oct 2019 07:16:20 +0100
Cc: Paul Hoffman <paul.hoffman@icann.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, Sandy Ginoza <sginoza@amsl.com>
X-Mao-Original-Outgoing-Id: 594022579.126771-7cbd5ce29beff87cca2f6199f060a94d
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB3B5D3A-2AFF-4ACE-BD71-D9EE2F9A4908@tzi.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> <d53ef90e-5a50-1472-a61e-12c7a417ac44@icann.org> <b19cd7de-6992-a3b5-ea23-929627018cc0@gmx.de> <019a4a58-ca92-0497-1155-303fba341241@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/RBpZ3HknLV1D-FTi91fozBAp76Q>
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:16:26 -0000

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.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email