[Rfc-markdown] New xml2rfc release: v2.10.0
Henrik Levkowetz <henrik@levkowetz.com> Thu, 12 July 2018 19:34 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 04357130F44; Thu, 12 Jul 2018 12:34:50 -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, 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 R49Ox-XPdECG; Thu, 12 Jul 2018 12:34:47 -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 B1D81130E2A; Thu, 12 Jul 2018 12:34:47 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1fdhMV-0002I0-Iu; Thu, 12 Jul 2018 12:34:47 -0700
To: xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1fdhMV-0002I0-Iu@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Thu, 12 Jul 2018 12:34:47 -0700
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: rfc-markdown@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/wCY-PqaQQK9aHxO82cMOLcEzHak>
Subject: [Rfc-markdown] New xml2rfc release: v2.10.0
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.27
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, 12 Jul 2018 19:34:50 -0000
Hi, This is an automatic notification about a new xml2rfc release, v2.10.0, generated when running the mkrelease script. Release notes: xml2rfc (2.10.0) ietf; urgency=medium This release introduces the vocabulary v3 text formatter. In order to invoke this formatter, use the regular --text switch for text output, and add the --v3 switch to specify the v3 text formatter. Xml2rfc in v3 text formatter mode accepts any valid xml2rfc input file, but since the actual formatter only understands the XML elements and attributes which have not been deprecated by RFC7991, it first applies the xml2rfc v2v3 converter in order to transform any deprecated markup to the elements and attributes it understands, and then applies the preptool in order to normalize the input before it starts rendering. This is the first release of the v3 text formatter, and there are some known rough edges and deficiencies: - The current table output renders all table borders. This differs from the v2 formatter, and will be remedied in a later release. The reason for doing the first release with this rendering of tables is that the table layout options have changed substantially with the possibility of using rowspans, and the table layout code is much more complex than for v2 as a consequence. With all table borders visible, the initial testing of the layout code has been easier than if horizontal borders were not rendered. - The statement of work for the text formatter coding does not include paginated output, and as a consequence the Table of Contents is much less informative than it would be if it was able to show the page for each ToC entry. - The xml2rfc v3 vocabulary (RFC 7991) does not provide 'align' attributes for tables, which means that the ability to center and right-align tables is lost. All tables are left-aligned. (Alignment of text within each cell is still supported, though.) - The index generation (using <iref> elements) has some known issues, which will also be fixed in a subsequent release. The v3 schema used in this release differs from the schema specified in RFC7991 in some respects. A separate document will be published with details about the changes: draft-levkowetz-xml2rfc-v3-implementation-notes. The issues leading to the changes will also be entered in the document issue trackers and sent to the xml2rfc-dev mailing list for discussion. Feedback on the v3 text formatter will be appreciated. Please send feedback to xml2rfc-dev@ietf.org or henrik@levkowetz.com. -- Henrik Levkowetz <henrik@levkowetz.com> 12 Jul 2018 12:29:39 -0700 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.10.0' Regards, Henrik (via the mkrelease script)
- [Rfc-markdown] New xml2rfc release: v2.10.0 Henrik Levkowetz