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, 05 November 2019 18:43 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 2011A12011C for <xml2rfc-dev@ietfa.amsl.com>; Tue, 5 Nov 2019 10:43:22 -0800 (PST)
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 ubQekhefd6lQ for <xml2rfc-dev@ietfa.amsl.com>; Tue, 5 Nov 2019 10:43:20 -0800 (PST)
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 B3737120115 for <xml2rfc-dev@ietf.org>; Tue, 5 Nov 2019 10:43:20 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:53045 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 1iS3nT-0000do-0u; Tue, 05 Nov 2019 10:43:19 -0800
To: Heather Flanagan <rse@rfc-editor.org>, Julian Reschke <julian.reschke@gmx.de>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.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> <D1535E4D-A260-477E-AF44-720C28801768@rfc-editor.org> <c551753e-7b28-0284-3ef8-bba884ea44f2@gmx.de> <6EAF86F8-C32F-434E-87ED-9E66043CC989@rfc-editor.org>
Cc: Carsten Bormann <cabo@tzi.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <6c67abbc-542d-f734-d462-658ae8ad0820@levkowetz.com>
Date: Tue, 05 Nov 2019 19:43:10 +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: <6EAF86F8-C32F-434E-87ED-9E66043CC989@rfc-editor.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Q10fjhonF4ftxpaGxBJPjLtGbgXI5BsH5"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, cabo@tzi.org, julian.reschke@gmx.de, rse@rfc-editor.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/RgrlYdgDUIkCvkQKMN6HUYiUjHI>
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:43:22 -0000

On 2019-11-05 19:35, Heather Flanagan wrote:
> 
>> On Nov 5, 2019, at 1:33 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> 
>> On 05.11.2019 19:30, Heather Flanagan wrote:
>>> ...
>>> 
>>> 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?
>>> ...
>> 
>> What happens if you put a <br> into a section title, and that gets
>> references in the TOC, or via <xref format="title"..:>"?
> 
> It is ignored within the TOC (but does change the output in the text)
> 
>> 
>> What happens if you put a <br> into a document title, and it appears
>> inside a <reference>?
>> 
> 
> It is ignored within the reference.

All of that works for me; straightforward and sensible.  I think all
of that matches what I do today for &br; .


	Henrik

v2.23.0 | Report a Bug | By Email