Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.31.0

Robert Moskowitz <rgm@htt-consult.com> Wed, 25 September 2019 21:32 UTC

Return-Path: <rgm@htt-consult.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 3A71412004E; Wed, 25 Sep 2019 14:32:05 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 h_XFQfrZu8Di; Wed, 25 Sep 2019 14:32:03 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B2A6120026; Wed, 25 Sep 2019 14:32:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id DD35E615EB; Wed, 25 Sep 2019 17:32:01 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id m16yIZqn7mPL; Wed, 25 Sep 2019 17:31:54 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 2C03A60029; Wed, 25 Sep 2019 17:31:52 -0400 (EDT)
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1iDE6u-0004WP-Ev@durif.tools.ietf.org> <445c7666-57bb-cb3b-f95e-e2186aea92a7@htt-consult.com> <0b295bd9-8f2a-6eb9-bf04-911f5635aeab@levkowetz.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <7031eb32-97b6-83f6-c359-7cb57d06fa64@htt-consult.com>
Date: Wed, 25 Sep 2019 17:31:44 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0
MIME-Version: 1.0
In-Reply-To: <0b295bd9-8f2a-6eb9-bf04-911f5635aeab@levkowetz.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/OxiwedLhz_XeHUeCJkLkK4oRK30>
Subject: Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.31.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: Wed, 25 Sep 2019 21:32:05 -0000

Hello Henrik,

On 9/25/19 5:09 PM, Henrik Levkowetz wrote:
> Hi Bob,
>
> On 2019-09-25 22:56, Robert Moskowitz wrote:
>> This does not fix my character problem (probably was not intended to do
>> that):
>>
>> $ xml2rfc draft-moskowitz-hip-new-crypto-01.xml
>> Warning: Illegal character replaced in string: &#128;
>> Warning: Illegal character replaced in string: &#147;
>>    Created file draft-moskowitz-hip-new-crypto-01.txt
> No, this release addressed some issues raised by the RFC-Editor staff.
>
> FWIW, if you intend to move to v3, the seriesInfo name (where the
> problem is, in this case) will not allow non-ASCII characters.  The
> most straightforward approach is to include the reference information
> in your document directly, and replace the unicode en-dash with an
> ASCII dash:
>
> <reference anchor='ASIACRYPT-2017' >
>    <front>
>      <title>Full-State Keyed Duplex with Built-In Multi-user Support</title>
>      <author initials="J." surname="Daemen" fullname="Joan Daemen">
>        <organization></organization>
>      </author>
>      <author initials="B." surname="Mennink" fullname="Bart Mennink">
>        <organization></organization>
>      </author>
>      <author initials="G." surname="Van Assche" fullname="Gilles Van Assche">
>        <organization></organization>
>      </author>
>      <date year="2017"/>
>    </front>
>    <seriesInfo name="Advances in Cryptology - ASIACRYPT 2017" value="pp. 606-637"/>
>    <seriesInfo name="DOI" value="10.1007/978-3-319-70697-9_21"/>
> </reference>

I will use this as a quick fix so I can get this submitted.

> The more general solution (which isn't available immediately) is that the
> bibxml7 script is modified to transcode non-ASCII punctuation to ASCII
> equivalents.

This sounds like the best path, as there will be other citations that 
will have non-ASCII codes.

> xml2rfc does this for body text, to avoid unnecessary issues with smart
> quotes etc., but it does not look at attribute values in reference entries
> when doing this.  I don't know, maybe it should.  Or maybe not.

But then if it is put into xml2rfc, it fixes it there and does not 
interfere with whatever else bibxml7 is used for?

Thanks

>
>
> Regards,
>
> 	Henrik
>
>
>
>> $ xml2rfc --version
>> xml2rfc 2.31.0
>>
>>
>> On 9/25/19 4:42 PM, Henrik Levkowetz wrote:
>>> Hi,
>>>
>>> This is an automatic notification about a new xml2rfc release,
>>> v2.31.0, generated when running the mkrelease script.
>>>
>>> Release notes:
>>>
>>> xml2rfc (2.31.0) ietf; urgency=medium
>>>
>>>     This release adds a feature to help with conditional line breaking
>>>     inside table cells, and tweaks the layout of text in cells slightly.  It
>>>     also fixes an incorrect line-break point and second-line indentation for
>>>     long section titles in the v3 text formatter.  From the commit log:
>>>
>>>     * Fixed an issue with leading and trailing space padding in table cells,
>>>       and refined it to consider the alignment setting.
>>>
>>>     * Modified the text formatter to accept &zwsp; as a potential line-break
>>>       point.
>>>
>>>     * Included zwsp in allowed special characters (in addition to nbsp, nbhy,
>>>       word-joiner and line-separator).
>>>
>>>     * Fixed the line-breaking and second-line indentation of section titles
>>>       in v3 text output.
>>>
>>>     * The start of an emacs nXML mode schema which explicitly mentions
>>>       xinclud in a couple of places.
>>>
>>>     * Removed code left in pdf.py by mistake, and set options.pdf=True when
>>>       in the PdfWriter.
>>>
>>>    -- Henrik Levkowetz <henrik@levkowetz.com>  25 Sep 2019 13:38:34 -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.31.0'
>>>
>>> Regards,
>>>
>>> 	Henrik
>>> 	(via the mkrelease script)
>>>
>>> _______________________________________________
>>> xml2rfc mailing list
>>> xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>