[Rfc-markdown] New xml2rfc release: v2.13.0

Henrik Levkowetz <henrik@levkowetz.com> Sat, 17 November 2018 13:25 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 50BDA1286E7; Sat, 17 Nov 2018 05:25:18 -0800 (PST)
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] 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 vTFnggsJUS-0; Sat, 17 Nov 2018 05:25:16 -0800 (PST)
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 3D02F130DE3; Sat, 17 Nov 2018 05:25:16 -0800 (PST)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1gO0b6-0000xf-0N; Sat, 17 Nov 2018 05:25:16 -0800
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1gO0b6-0000xf-0N@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Sat, 17 Nov 2018 05:25:16 -0800
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/_ptFM-_bQMFh7ueC1ybjViJKrG0>
Subject: [Rfc-markdown] New xml2rfc release: v2.13.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: Sat, 17 Nov 2018 13:25:18 -0000

Hi,

This is an automatic notification about a new xml2rfc release, 
v2.13.0, generated when running the mkrelease script.

Release notes:

xml2rfc (2.13.0) ietf; urgency=medium

  This release provides an number of improvements.  Rendering of all v3
  elements should now be in place for the v3 text and html formatters, and
  the renderers have been updated to follow the issue resolutions so far.
  A bug in the generation of boilerplate for BCPs has been fixed.  Feedback
  on unexpected postal address data has been improved, as has feedback on
  unexpected combinations of stream, category, and consensus settings.

  Details from the commit log:

  * In the html formatter:

    - Added indentation support for <dl> to the v3 html renderer.  

    - Fixed a bug in the display of author names in the author addresses
      section when no postal information is given.  

    - Improved <eref> rendering for the case when no eref text is provided.  

    - Corrected the anchor placement for slugified names of figures and
      tables.  

    - Added support for <referencegroup>.  

    - Added a missing CSS class for <seriesInfo> rendering.  

    - Added support for right and center alignment of tables.

  * In the text formatter:

    - Added v3 text formatter support for rendering of blockquote and cref.  

    - Minor other tweaks.

  * In the preptool: 

    - Added support for <referencegroup> elements.  

    - Added support for the <rfc> version attribute.  

    - Fixed a string formatting bug.  

    - Added attribute valididty checking for integer-valued attributes.  

    - Removed the forced inclusion of day for RFC publication dates, reverting
      to permitting publication with only year and month.

    - Added more sophisticated checking and setting of consensus, based on
      what is valid for the given stream and category.  

    - Refined the handling when given input that already contains boilerplate,
      authors addresses and index.

  * In the v2v3 converter:

    - Added setting of the <rfc> version attribute.

    - Removed dubious elimination of <format> elements pointing to alternative
      reference URLs.

    - Fixed a couple of instances of buggy error reporting.

  * Changed util.postal.get_normalized_address() to return a filled-in adr 
    structure even if no country could be identified, for more consistent code 
    in other places.

  * In the Relax NG schema files:

    - Changed the v3 schema default value for <dl> newline so that the effect 
      is the same as for the old 'hanging' default value.

    - Added a 'derivedAnchor' attribute for <referencegroup>, matching that of
      <reference>.

  * In the CSS style sheet:

    - Changed the CSS class for Reference Section definition lists from
      'reference' to 'references'.  

    - Added styling for table alignment and
      applied the same styling for table labels as for figure labels.

  * Added bcp14, em, iref, strong, sub, and sup to the permitted elements 
    in <name>.

  * Fixed some issues with the error messages for combinations of stream, 
    category, and consensus.

  * Added code to honour the "display" attribute of <cref>.

  * Added a preptool action to check the <rfc> attributes submissionType 
    (i.e., stream), category, and consensus for validity.  Invalid combinations 
    are called out, and warnings are issued about setting missing settings to 
    default values.

  * With v2 formatters, treat consensus for BCPs the same way as STD 
    documents, 

  * Refactored some logging and address functionality, improved address
    warnings and other address-related tweaks.

 -- Henrik Levkowetz <henrik@levkowetz.com>  16 Nov 2018 21:28:06 +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.13.0'

Regards,

	Henrik
	(via the mkrelease script)