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

Carsten Bormann <cabo@tzi.org> Sat, 05 October 2019 07:05 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 279CC1200DE; Sat, 5 Oct 2019 00:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 IVdepE4blKMr; Sat, 5 Oct 2019 00:05:46 -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 30FC41200EB; Sat, 5 Oct 2019 00:05:46 -0700 (PDT)
Received: from [192.168.34.217] (h-164-71.A137.corp.bahnhof.se [37.123.164.71]) (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 46ld7C67Q1zyky; Sat, 5 Oct 2019 09:05:43 +0200 (CEST)
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: <CANMZLAYTck-0_Jv0boSa_wPeZ8G26uBtJaEmwpybD5AFnqYCqA@mail.gmail.com>
Date: Sat, 5 Oct 2019 09:05:43 +0200
Cc: Miek Gieben <miek@miek.nl>, Julian Reschke <julian.reschke@gmx.de>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
X-Mao-Original-Outgoing-Id: 591951941.0511611-7ebf700609c5ac673641a3764ad9b250
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F0B71A5-82EC-43EF-B207-3E95F636EDB0@tzi.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <8304e61d-c550-91ea-9e23-eef2cd31240b@gmx.de> <A3513970-EEB0-4DBD-9E6F-A87EBFAF886D@att.com> <de4feaff-8f71-cd38-545c-2d848749251b@levkowetz.com> <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> <20191005061759.GA23541@miek.nl> <CANMZLAYTck-0_Jv0boSa_wPeZ8G26uBtJaEmwpybD5AFnqYCqA@mail.gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/0GUoKTmwVh6gCxSemR0AEmgDsE8>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Oct 2019 07:05:49 -0000

On Oct 5, 2019, at 08:40, Brian Carpenter <brian.e.carpenter@gmail.com>; wrote:
> 
> Sorry, outlawed by who, in which RFC?

That is a good summary of the discussion of the year so far.

(If anyone wonders why I’m so slow to pick up v3 in kramdown-rfc:
It is just too hard to guess what v3 actually is.
And it’s changing, while stability of the authoring format is the whole point of kramdown-rfc.
So generating v2-v3 and hoping that the RFC editor will bang the v3 derived from it into shape is the best transition strategy right now.)

Grüße, Carsten