IETF Logo Mail Archive

Re: [Rfc-markdown] [Tools-discuss] Xml2rfc regression?: rfc2629.dtd (emergency fix in 1.5.25)

Carsten Bormann <cabo@tzi.org> Tue, 25 January 2022 07:35 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 A13613A0D1E; Mon, 24 Jan 2022 23:35:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 LMJEtZYJEw-R; Mon, 24 Jan 2022 23:35:37 -0800 (PST)
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 2F3AA3A0D1C; Mon, 24 Jan 2022 23:35:36 -0800 (PST)
Received: from smtpclient.apple (p5089a6b7.dip0.t-ipconnect.de [80.137.166.183]) (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 4JjdtX0gcTzDCc9; Tue, 25 Jan 2022 08:35:32 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <b60636f5-d825-43f3-968b-f4e8319d5e23@beta.fastmail.com>
Date: Tue, 25 Jan 2022 08:35:31 +0100
Cc: tools-discuss <tools-discuss@ietf.org>, rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <44F93444-5714-4CD6-A5AD-3E056895D69B@tzi.org>
References: <81E41F85-E62B-4329-83AE-F84C4AB3165A@tzi.org> <d68b79c6-2240-89e0-fb24-47c35e9a8b3f@staff.ietf.org> <29409D64-A1A8-45DA-8757-64D5EB304C1A@tzi.org> <b60636f5-d825-43f3-968b-f4e8319d5e23@beta.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/jlJ1Yg7sfZnzRAUHQdqjBSxQj8k>
Subject: Re: [Rfc-markdown] [Tools-discuss] Xml2rfc regression?: rfc2629.dtd (emergency fix in 1.5.25)
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: Tue, 25 Jan 2022 07:35:42 -0000


> On 25. Jan 2022, at 08:00, Martin Thomson <mt@lowentropy.net> wrote:
> 
> On Tue, Jan 25, 2022, at 17:24, Carsten Bormann wrote:
>> I did an emergency fix in kramdown-rfc 1.5.25 that substitutes
> 
> Thank you.  Consider making that permanent.  

I think with the “doctype-reference” escape valve the fix can stay in.

> Having to build an XML catalogue just to do simple XML processing (extracting author names, say) is an annoying hurdle to clear.  

I agree; kramdown-rfc just kept chugging along with most of the first ~50000 XML drafts out there, and this is now gone.

> Inline declarations for entities is probably unnecessary for the output of a tool (UTF-8 does just work), but I do find it easier to distinguish various types of space if entities are used when it isn't U+20.

Yes.  I wish Emacs were better in showing these types (of course, I'll just need to configure it right :-).

I have no idea what made the four entities that are now inserted by the v2v3 conversion so special; these of course highlight the inconsistent application of RFC 7997.
(Ceterum censeo: I want my dashes…)

> Can you push your change please?

Sorry, done.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email