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

Henrik Levkowetz <henrik@levkowetz.com> Thu, 14 February 2019 14:20 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 9AD7B13106D; Thu, 14 Feb 2019 06:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id BvWrSQ-oYnYx; Thu, 14 Feb 2019 06:20:33 -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 4D342130F0E; Thu, 14 Feb 2019 06:20:33 -0800 (PST)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1guHsP-0006fN-5z; Thu, 14 Feb 2019 06:20:33 -0800
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1guHsP-0006fN-5z@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Thu, 14 Feb 2019 06:20:33 -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/-vbb8denYSXxETPohXAlfO2ySpA>
Subject: [Rfc-markdown] New xml2rfc release: v2.19.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: Thu, 14 Feb 2019 14:20:36 -0000


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

Release notes:

xml2rfc (2.19.0) ietf; urgency=medium

   **Changed handling of alternative artwork**

   The way <artwork> has been specified to handle the presence of both
   SVG artwork and text fallback (in Section 2.5 of [RFC7991]) has the
   result that any SVG content has to be placed as a data: URL in the
   "src" attribute when an ascii-art fallback is present.  This makes
   the SVG effectively uneditable once the preptool has been run, even
   if the SVG artwork was originally provided as a regular SVG XML file
   external to the document XML file.

   In order to be able to more easily deal with alternative instances of
   artwork, and in the future possibly deal smoothly with a wider number
   of alternative artwork formats than is currently provided for, a new
   element <artset> could be introduced, presenting a set of alternative
   artwork executions.  This would let the renderer pick the most
   appropriate <artwork> instance for its format from the alternatives
   present within an <artset> element, based on the "type" attribute of
   each enclosed <artwork> element.

   If more than one <artwork> element is found within an <artset>
   element, with the same "type" attribute, the renderer could select
   the first one, or possibly choose between the alternative instances
   based on the output format and some quality of the alternative
   instances that made one more suitable than the other for that
   particular format, such as size, aspect ratio, or whatnot.

   Implementation:  Xml2rfc as of version 2.18.0 implements this, with a
      preference list when rendering to HTML and PDF of ( "svg",
      "binary-art", "ascii-art" ), while the text renderer uses the list
      ( "ascii-art", ) -- i.e., one entry only.  The Relax-NG compact
      schema used for <artset> is this::

        artset =
          element artset {
            attribute xml:base { text }?,
            attribute xml:lang { text }?,
            attribute anchor { xsd:ID }?,
            attribute pn { xsd:ID }?,

      The <artset> element can occur anywhere an <artwork> element can
      occur.  The first anchor on an <artwork> element within an
      <artset> element will be promoted to the <artset> element if it
      has none; apart from that, anchors on <artwork> elements within an
      <artset> element will be removed by the preptool.

   Additionally, this release contains some other fixes and changes.  From
   the commit log:

  * Normalized the expansion of <xref> to be more consistent conceptually 
    and across renderings.  Added back rendering support for format='none'.

  * Added another exception class to the import exception catch for pango,
    to avoid a crash in some environments.

  * Applied a patch from rjs@nostrum.com to improve the xml2rfc description.

  * Disallow lxml 4.3.1, as it can cause segfaults with some Python 
    versions.  Fixes issue #393.

  * Put back LICENCE which has been lost from the source distribution tarball
    at some point.

  * Adjusted the <xref format="counter"/> output for appendices.

  * Added code to remove any usage of Unicode U+2028 LINE SEPARATOR from the
    text output also in legacy mode.

  * Fixed a problem with the text format rendering of <xref> for an appendix.

  * Added a get_element_tags() method in BaseV3Writer, and commented out 
    some debug code.

  * Removed a warning about missing country that would appear even if no 
    <address> or <postal> was supplied.

 -- Henrik Levkowetz <henrik@levkowetz.com>  12 Feb 2019 16:43:44 +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

The new version is also available through SVN checkout, with
  'svn checkout http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.19.0'


	(via the mkrelease script)