[Rfc-markdown] 1.4.1: Housekeeping release

Carsten Bormann <cabo@tzi.org> Mon, 22 March 2021 16:36 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 []) by ietfa.amsl.com (Postfix) with ESMTP id B3F9C3A0EFA for <rfc-markdown@ietfa.amsl.com>; Mon, 22 Mar 2021 09:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bYUADZcaNR-b for <rfc-markdown@ietfa.amsl.com>; Mon, 22 Mar 2021 09:36:54 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 382C13A0E66 for <rfc-markdown@ietf.org>; Mon, 22 Mar 2021 09:36:42 -0700 (PDT)
Received: from [] (p548dc178.dip0.t-ipconnect.de []) (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 4F40WW4CYcz17cs; Mon, 22 Mar 2021 17:36:39 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 638123799.019226-10a48eb67d40e2dc9434f0a8d85c827e
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Mon, 22 Mar 2021 17:36:39 +0100
Message-Id: <378019D2-9268-4997-91FA-5C180B68B775@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/s6JAdHj6bLXAdnW3_vLmgt2TmHE>
Subject: [Rfc-markdown] 1.4.1: Housekeeping release
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: Mon, 22 Mar 2021 16:37:01 -0000

1.4.1 syncs back to current upstream kramdown release (from 1.17.0 to 2.3.1); I used the opportunity to bump up the minor version.

This was on hold for a while because it was not clear whether the major version transition from 1.x to 2.x would make a difference.  I now believe the changes are not relevant for RFC writing.

… with one exception: kramdown 2.3 removed support for processing instructions (as they are not in HTML 5).  Since PIs have been part of RFCXML from the start, there are likely to be many markdown documents out there that use them.  So I moved the deleted support from upstream into kramdown-rfc; there should be no difference in behavior from the 1.3.x releases.

There is one bug fix in upstream 2.3.1 that might be relevant; it is about

   ` `

(a solitary space in backquotes).  See https://github.com/cabo/kramdown-rfc2629/issues/108 for the gory details and the upstream https://github.com/gettalong/kramdown/issues/704 for the “fix” (which just makes the surprising behavior consistently surprising, but maybe the above construct is already a bit outlandish as the space is nearly invisible in HTML).

As usual, update with

	gem update

… and tell us about any issues at https://github.com/cabo/kramdown-rfc2629/issues or here.

Grüße, Carsten