[Rfc-markdown] 1.3.29: Do not use server-side anchor setup for stand_alone: true

Carsten Bormann <cabo@tzi.org> Fri, 12 February 2021 16:49 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 E0BAC3A17AE; Fri, 12 Feb 2021 08:49:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 6jCYK20qKSCI; Fri, 12 Feb 2021 08:49:44 -0800 (PST)
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 512C73A17A7; Fri, 12 Feb 2021 08:49:43 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (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 4Dcfc52wL6zyhc; Fri, 12 Feb 2021 17:49:41 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
Date: Fri, 12 Feb 2021 17:49:40 +0100
Cc: tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 634841380.868253-fcdf41356b42baf7c61785694eded207
Content-Transfer-Encoding: quoted-printable
Message-Id: <E231E85C-1129-4855-920E-6BE92E9FEEC9@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/ULcRqY4odJP3lBHeXJdnmXsbqhc>
Subject: [Rfc-markdown] 1.3.29: Do not use server-side anchor setup for stand_alone: true
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: Fri, 12 Feb 2021 16:49:48 -0000

This is an emergency workaround for the tools server problem discussed in
<https://mailarchive.ietf.org/arch/msg/tools-discuss/VqTXuUNnpQJE5rB5_JfU71rMMoo>

Please use `stand_alone: true` in the YAML header to benefit from this (*).

A few minor fixes (and a new feature) were also done recently that I hadn’t announced:

1.3.28: SVG error handling fixes
1.3.27: Add -i option to kdrfc, run idnits
1.3.26: Avoid dependency for module that needs native build
1.3.25: Work around ERB api deprecation

Grüße, Carsten

(*) actually, preferably always use stand_alone: true, unless you have a broken proxy setup that makes it difficult for you to access the bibxml servers.