Re: [Rfc-markdown] V3 weird stuff, was: Carsten: Re: [rfc-i] summary of Removing postal information from RFCs
Carsten Bormann <cabo@tzi.org> Thu, 22 July 2021 00:53 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 5A0883A30F3
for <rfc-markdown@ietfa.amsl.com>; Wed, 21 Jul 2021 17:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, 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 Gumd6G7M0hys for <rfc-markdown@ietfa.amsl.com>;
Wed, 21 Jul 2021 17:53:52 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de
[IPv6:2001:638:708:32::15])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 30DDE3A30F2
for <rfc-markdown@ietf.org>; Wed, 21 Jul 2021 17:53:52 -0700 (PDT)
Received: from smtpclient.apple (p548dcc89.dip0.t-ipconnect.de
[84.141.204.137])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GVYqL5F8Hz31Lw;
Thu, 22 Jul 2021 02:53:50 +0200 (CEST)
Content-Type: text/plain;
charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <f09f5b59-219f-052b-8af6-59f2aed64291@gmx.de>
Date: Thu, 22 Jul 2021 02:53:50 +0200
Cc: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A124FCC8-FBD1-4F58-B345-85F2A7657C62@tzi.org>
References: <20210712034838.B461E209AFFB@ary.qy>
<6c781dab-7a40-7031-be1c-d77a182f4cf4@gmail.com>
<DE0CD982-D4BE-44A6-9234-B53A756E9717@mnot.net>
<bbb8302a-4041-35db-ce61-d2a18b8ebeee@taugh.com>
<AB6E5013-C14E-4962-8907-17F241971F9D@tzi.org>
<20210719171839.GB24216@faui48e.informatik.uni-erlangen.de>
<DBCC4252-8A2D-473C-82CD-B1B2688586D3@tzi.org> <15571.1626787687@localhost>
<65E34C78-8090-4534-8046-7E271B0ED07A@tzi.org>
<BA4E84AD-22C2-470F-A41D-09942DF33B00@ietf.org>
<E22C5330-FDD0-406A-865D-5D393CC78D26@tzi.org>
<f09f5b59-219f-052b-8af6-59f2aed64291@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/E6qQwFQO5GoIDGNqJR79X4GdDsU>
Subject: Re: [Rfc-markdown] V3 weird stuff,
was: Carsten: Re: [rfc-i] summary of Removing postal information
from RFCs
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: Thu, 22 Jul 2021 00:53:57 -0000
On 21. Jul 2021, at 19:34, Julian Reschke <julian.reschke@gmx.de> wrote: > > Could you elaborate on "the rather broken content model of <li>”? Sorry, it’s been a while. I started converting kramdown-rfc’s ol/ul to v3 and ran into an issue, which made me stick with v2 syntax, letting xml2rfc do the work. Don’t remember what it was. I seem to remember there is still one bug in xml2rfc here, as well. (These things pop up when I’m trying to do something else… I don’t always take good notes when I’m at yak shaving stack depth 5 already.) Grüße, Carsten
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Michael Richardson
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Miek Gieben
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Jay Daley
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- [Rfc-markdown] V3 weird stuff, was: Carsten: Re: … Julian Reschke
- Re: [Rfc-markdown] V3 weird stuff, was: Carsten: … Carsten Bormann
- [Rfc-markdown] No longer need to run xml2rfc --v2… Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Julian Reschke
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Julian Reschke