[Rfc-markdown] New xml2rfc release: v2.25.0
Henrik Levkowetz <henrik@levkowetz.com> Mon, 26 August 2019 12:44 UTC
Return-Path: <henrik@levkowetz.com>
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 2A7B512082C; Mon, 26 Aug 2019 05:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 5AVu0viRG_wx; Mon, 26 Aug 2019 05:44:26 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1876112021C; Mon, 26 Aug 2019 05:44:26 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i2EMD-0002SA-UW; Mon, 26 Aug 2019 05:44:25 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1i2EMD-0002SA-UW@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Mon, 26 Aug 2019 05:44:25 -0700
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/fLe7Aw3fPOcJNzAYA-nV6hX9H8A>
Subject: [Rfc-markdown] New xml2rfc release: v2.25.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: Mon, 26 Aug 2019 12:44:36 -0000
Hi, This is an automatic notification about a new xml2rfc release, v2.25.0, generated when running the mkrelease script. Release notes: xml2rfc (2.25.0) ietf; urgency=medium This rounds up the remaining known issues raised by the RFC Editor staff. Commit log excerpt: * Rolled back an earlier requirements change, and added a restriction on pycountry due to a buggy release. * Fixed a number of issues with the xml generated for ToC and Index. This makes the ToC output from prepped files the same as from unprepped files, which was not the case earlier. * Fixed an log() argument error. * Modified test input files to silence known issues with legacy rfc xml test files, in order to more easily be able to see newly appearing errors. * Fixed a string formatting error. Fixes issue #417. * Changed processing progress messages to more consistently obey --quiet, and to be visually distinct from errors and warnings. * Modified the PI stripping so as to be able to silence warnings during preptool processing. * Added indentation handling for variations of <ol> on request from the rfc-editor staff. * Moved the check for appropriate <bcp14> content from the text renderer to the preptool, and tweaked it to permit , e.g., 'MUST NOT'. * Added a base_url setting to avoid an error message during pdf generation. * Added an option --id-reference-base-url to set base url for rendering of <xref> with I-D section references, with a sensible default; and set a default value for --rfc-reference-base-url for <xref> with section= ease of use. * Tweaked the conditions for a preptool warning about missing docName to only apply in non-rfc mode, and added generation of any missing <link rel='prev'> element from docName if present. * Widened the search for seriesInfo elements when handling the --rfc-reference-base-url option, in order to handle all possible placements, and fixed a bug in the creation of target URL when using this option. * Added a warning for <vspace> elements without proper v3 alternatives during v2v3 conversion. * Fixed a bug introduced in [3201] when stabilizing attribute order, which could cause errors when running v2v3 conversion with XInclude insertion. * Changed the code for --info dump to work for both py27 and py3x. * The --legacy-list-symbols option was checked for validity before the version attribute of the input file was seen. Moved this check (and some similar cases) later, in order to permit it to be used with v3 input without giving the --v3 option. Fixes issue #414. -- Henrik Levkowetz <henrik@levkowetz.com> 24 Aug 2019 22:02:32 +0000 The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. The new version is also available through SVN checkout, with 'svn checkout http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.25.0' Regards, Henrik (via the mkrelease script)
- [Rfc-markdown] New xml2rfc release: v2.25.0 Henrik Levkowetz
- [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2… Julian Reschke
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Miek Gieben
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Henrik Levkowetz
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc] bcp14, was: [xml2rfc… Fred Baker
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Dave Lawrence
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Henrik Levkowetz
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Sparks
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Sparks
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Henrik Levkowetz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Henrik Levkowetz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Carsten Bormann
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Carsten Bormann
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Carsten Bormann
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Julian Reschke