IETF Logo Mail Archive

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

Heather Flanagan <rse@rfc-editor.org> Tue, 05 November 2019 18:30 UTC

Return-Path: <rse@rfc-editor.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 1F8FE120142 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 5 Nov 2019 10:30:15 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 D1psQpabeLXt for <xml2rfc-dev@ietfa.amsl.com>; Tue, 5 Nov 2019 10:30:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57E2212013A for <xml2rfc-dev@ietf.org>; Tue, 5 Nov 2019 10:30:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id A311BF40716; Tue, 5 Nov 2019 10:29:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TuDPWedM_CGU; Tue, 5 Nov 2019 10:29:55 -0800 (PST)
Received: from [IPv6:2620:f:8000:210:88d7:6470:4b0:5ef4] (unknown [IPv6:2620:f:8000:210:88d7:6470:4b0:5ef4]) by rfc-editor.org (Postfix) with ESMTPSA id B720DF40710; Tue, 5 Nov 2019 10:29:54 -0800 (PST)
From: Heather Flanagan <rse@rfc-editor.org>
Message-Id: <D1535E4D-A260-477E-AF44-720C28801768@rfc-editor.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0E3B2EBE-65A1-4554-8E4A-E58DE97B8310"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Date: Tue, 05 Nov 2019 13:30:10 -0500
In-Reply-To: <6723154e-9bf1-d8ce-c8bd-a681fec1de5a@gmx.de>
Cc: Henrik Levkowetz <henrik@levkowetz.com>, Carsten Bormann <cabo@tzi.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
To: Julian Reschke <julian.reschke@gmx.de>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <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> <4911a729-648a-a6c7-e673-4dd0fc0cadac@levkowetz.com> <908decb8-c24c-238d-2e27-982aa587d321@gmx.de> <0f5b5e73-bcca-0ff5-570d-c1622891dcf8@gmx.de> <703F1E91-C9E0-42BD-927C-D0D65D8CF7B0@rfc-editor.org> <6723154e-9bf1-d8ce-c8bd-a681fec1de5a@gmx.de>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/oe-YD4rDFaXdSgmSpHhXyk6PXPk>
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, 05 Nov 2019 18:30:15 -0000


> On Nov 5, 2019, at 1:24 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 05.11.2019 18:16, Heather Flanagan wrote:
>> 
>> 
>>> On Nov 4, 2019, at 1:21 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>>> 
>>> On 29.10.2019 08:04, Julian Reschke wrote:
>>>> ...
>>>> As a first step, I'd make it available exactly where the production
>>>> center needs it right now, so that the publication process can proceed.
>>>> 
>>>> (I think that means "in <t>" right now)
>>>> ...
>>> 
>>> ...and that would fix the issue for the document in AUTH48, and also
>>> would allow a workaround for contributor insertion that doesn't require
>>> <artwork>.
>>> 
>>> Another week has passed. How can we make progress here? Heather?
>>> 
>>> Best regards, Julian
>>> 
>> 
>> Make <br> generally available, and trust the RPC to use it wisely.
> 
> It's not that easy.
> 
> If you allow it everywhere, you need to define how it behaves
> everywhere, both for display, and when it gets referenced.
> 

It should tell the output formatter to put in whatever break is appropriate to that format that will cause the next words to go to a new line.

Is that what you’re talking about?

-Heather

v2.23.0 | Report a Bug | By Email