
From nobody Sun Sep  1 09:51:44 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E42B712002F; Sun,  1 Sep 2019 09:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 sQYqQQ89QpWO; Sun,  1 Sep 2019 09:51:34 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69D01120025; Sun,  1 Sep 2019 09:51:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1567356675; bh=kCaZs7ndxP9PTOjLMGsqI7RPRXc/+n9XT83/wUSr03A=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=ZfVS+L6vyb9sCfcQe5o6atm5XBrr58qZF4Tmd/AwkO/1NujTCoNsA/Xcnb7DQIQSH vN5dx02Y3Xbmh6iiJI2fKmwYIFKtzQ7RnxADlarcyE2xQpLwVWY8+xtqUmtikGH1h3 oMJDZIlz3CMzybmcR0mRv9r/LpniX1nO8UFQe1R0=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.132.77]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MbfnB-1hncVa25Lh-00J2NR; Sun, 01 Sep 2019 18:51:15 +0200
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1hwTDm-00064V-6E@durif.tools.ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <add95758-94ee-00cc-74af-70629c962097@gmx.de>
Date: Sun, 1 Sep 2019 18:51:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <E1hwTDm-00064V-6E@durif.tools.ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:IHfD2Zbp8fdBDhcqFeYnlsEuEQEXDy10fNROrDfTRxnJevs0PQP tvCslaBFzMY1aI3t1XoVEfLeU512QFieog3OOXHXHi/ID8jbEBSaw4rdlDCAkjyOVGOMKbd 099TobP8DnAlJRIL3aHa/EhY96okeeIuNCF8Ou3LlVpo4D9F7+AQg1AtVejGaR0+XmsRtaQ s6DDSPmzi0MQSUsLOBSEg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:Tr4kVaXwi2c=:1dhdq+ptk1kv7OmLpZAmml TurKkcexw9PaiE697BT4qImwQL5MyhVHSrOw+uswBJ1z8TNrMd6tq24uvuJ8gHwoftbMRteGT qc1ZVeTz2gFdE6ZsMmq6yVl/fG/FCQEDcU8Ox0wsQCQ9cHfn/N/QAd/jrz13eFJREaGcN37FG 2R0N09OJie8YFe51Vog1sPeSbZneT19iRfFAqf1gqMz5P9vQvYYwPGBxXi+Y96RgfI/WRwsXe ghXmU22bL/oZ1BlZptJ5eReK2eBXySRo206UWwNSs+7u9u/7QG7p0OONwBaNMgAsWdbDKe6aR bXVkHuOzXViBCjdHAzN72/zWQ4oEjGM2hfCmIISDMFwG0LlG+Hux1mAw9lcDlILk3K5E0oHdp muPZpzHizCAB73AMG+8/S2ncrd5VsjaTe9PtknAFhy4Ea0ILuLiOnDRwYvmLb0NT9OSl0qRP3 0/1fdTzmxUA3VvHGWL+CBAQWfKqJpAby4Slgh/SAF+gXj5QqYS3GWiILV5gRfKyiEFAYVLumP enxkaDH1gXHytBnp2Q2B9Wdg7cDWzVlAEbC9txB8WzW48wMMOeH/EVPsGHoaob5YuOv/LkDRK 1DbdOLn7/XB2iGDsTmO5DUnWharjlFTS1M5oBnYUbolnR179cG/rbYdiqT3guYX2KnBdOsDD6 IUBaRvuA55u/F2P1RcUUir3XXkguTrshtR+YQYE/GevuSTjooFPKjnojPGglEeGa88bVRWVyq eofnIGTAgGiLEJhMybZbMFuMqe1tJP/RZGwQURglln0JgNjNSxOSYerg1mQvVTOSjzbnreWW5 fOn+ofgoW3rdst8dyGU6mmHssQR6z1z9bjGmSL9gkEn760IlXSP1ezPWbSS2wr7paEYM02csI ijWqHySlil2dHkD/FJdifcFtbnZY8K+++s0HhQozAT5W/rkRlYd8hF/HPUPdzbwHBb7tIB3hw A6+ash5x+LSwqIpb+O+15wpdbEhj8zOa9aXn8T+ckR05/vV1K7w4v4IXbBN0OWSAKTddcI41D n8xhiYMNFJlcE7CGNk3Fmgh0GdWoLgXCW+y+iJwSaU2lu/rAPzY/pKkZat0bsZgkrzM/OSqJC GRg/yzmvPMrb9uBHeErhkr/gMsjHrQ+u76gJZj3xQ+CjdnIMIV0Qzb0JW6JmGFjyttU26Sln3 5F5GwcZXSYrwzLwnSMniIIeHShiru6UVuwroGHeYKviVVZMQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/ND5PXhwdC1WH_AwdUp0PR8WEC10>
Subject: [xml2rfc-dev] vague dates, was: [xml2rfc] New xml2rfc release: v2.24.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2019 16:51:37 -0000

On 10.08.2019 17:23, Henrik Levkowetz wrote:
> ...
>    * Tweaked the <date> handling to make year ranges and fuzzy dates pos=
sible.
> ...

...as proposed in
<https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-not=
es-09#section-4.1.3.2>.

I believe this is a good change (and I have implemented in rfc2629.xslt,
see
<https://github.com/reschke/xml2rfc/commit/8596c0ffd14a7743621252d0bbfe0ba=
3acad1e2e>).

That said, we should clarify:

- that this applies only to <date> below <reference> elements
- what should happen when both text content and attributes are present
(rfc2629.xslt only takes the text content when no non-empty attributes
are present).

One comment on
<https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-not=
es-09#section-4.1.3.2>:

>    The text regarding prose text for month and year in bibliographic
>    references is not workable.  How should month and year be combined?
>    Some bibliographic references may have date text which requires year
>    first, others year last, and so on.  Mixing the described fuzziness
>    into the otherwise strict year, month, date format makes little sense
>    when the result of combining the year, month and date attributes
>    cannot be predictably and correctly rendered.

That's not a big issue in practice; just cram everything into the year
attribute, and do not set the others. Yes, this is a hack, but it works,
and has been used in the past (I can provide concrete numbers from
AUTH48 if people want to see them).

Final thoughts:

- in theory this could be used for specifying the dates of April 1st
RFCs (but I believe the approach proposed in
<https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/30> is
better)

- the RFC style guide should be clear about what to do for undated
references, and this ("vague" dates) might be useful for that

Best regards, Julian


From nobody Tue Sep  3 12:58:16 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85574120047; Tue,  3 Sep 2019 12:58:06 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 rT-EMGBZ6ZDZ; Tue,  3 Sep 2019 12:58:04 -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 A2AA6120043; Tue,  3 Sep 2019 12:58:04 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i5EwG-00014Q-GV; Tue, 03 Sep 2019 12:58:04 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1i5EwG-00014Q-GV@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Tue, 03 Sep 2019 12:58:04 -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/xml2rfc-dev/fxAX0EhLMhHqId7WqdxY1nz0XxE>
Subject: [xml2rfc-dev] New xml2rfc release: v2.26.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 19:58:07 -0000

Hi,

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

Release notes:

xml2rfc (2.26.0) ietf; urgency=medium

  * Fixed a broken rendering of Obsoletes: and Updates:, broken in different 
    ways in v3 HTML and v3 text output.  Fixes issue #423.

  * Added an alternative style sheet from Martin Thomson (reachable with
    --css=mt) and rewrote the code to read in alternative style sheets to look
    in more places. Also added a mt.js file to go with the mt.css file, and
    tweaked the html renderer to load an alternative .js file if an
    alternative .css file is set and a matching .js exists.

  * Fixed an issue with nested <ul> with emtpy="true".

  * Added a test, with error exit, for duplicate <displayreference> 
    replacement terms.  Fixes issue #421.

  * Changed the rendering of Internet-Draft references to follow
    draft-flanagan-7322bis-03 (RFC Style Guide bis) more closely.

  * Made the address pane for authors' addresses wider, to accomodate very 
    long email addresses.  Changed the bottom margin for some styles used by 
    figures in order to get the same caption placement for figures and tables.

  * Removed the computed <dl><dd> text mode indentation, and replaced it 
    with a fixed indentation of 3.

  * Added an example section using <aside> to element.xml.  Updated the 
    <xref> examples that use the section attribute.

  * Updated the prepping and rendering of <xref> with section settings to
    better handle sectionFormat="bare", and changed the handlin of the
    metadata.js script in HTML output.

  * Added a minified version of the metadata.js script, updated the help text
    for the --external-css switch, and changed the default for the
    --metadata-js-url switch to use the minified metadata.js file, and changed
    the metadata_js_url setting for invocation of xml2rfc renderers as library
    modules to use the minified metadata.js

  * Updated metadata.js with a new copy received from the RFC Editor staff.

  * Added a warning for mismatch between <rfc number="..."> and 
    <seriesInfo name="RFC" value="...">.

  * Modified the v2v3 conversion code to deal correctly with multiple 
    instances of <artwork> within an unlabelled Figure.  Modified the converter 
    to avoid some lxml-related issues under python 3.x.

  * Updated XmlRfc.__init__() with a new keyword argument to set source 
    file, needed when using the v2v3 converter as a library function (such as 
    from id2xml in v3 mode).

  * Incorporated a new updated copy of the original CSS stylesheet received 
    from the original contractor.

 -- Henrik Levkowetz <henrik@levkowetz.com>  03 Sep 2019 12:56:52 -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.26.0'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Tue Sep  3 13:55:39 2019
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 657CC12004E; Tue,  3 Sep 2019 13:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 w0BmzoI3VJAp; Tue,  3 Sep 2019 13:55:29 -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 095ED120045; Tue,  3 Sep 2019 13:55:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 7F23A62117; Tue,  3 Sep 2019 16:55:27 -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 i15umDch2Clw; Tue,  3 Sep 2019 16:55:23 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id DF1D5620EE; Tue,  3 Sep 2019 16:55:20 -0400 (EDT)
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1i5EwG-00014Q-GV@durif.tools.ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <1d7e7040-d294-a5e0-ddac-399bf84578bb@htt-consult.com>
Date: Tue, 3 Sep 2019 16:55:12 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <E1i5EwG-00014Q-GV@durif.tools.ietf.org>
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/xml2rfc-dev/PfEEMCn41FcH1j1ANLnTdkFxuhc>
Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.26.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 20:55:31 -0000

On 9/3/19 3:58 PM, Henrik Levkowetz wrote:
> Hi,
>
> This is an automatic notification about a new xml2rfc release,
> v2.26.0, generated when running the mkrelease script.
>
> Release notes:
>
> xml2rfc (2.26.0) ietf; urgency=medium
>
>
>    * Fixed an issue with nested <ul> with emtpy="true".
>
>

Gee, I hope this is not the way it is spelled in the code...

:)



From nobody Tue Sep  3 14:17:49 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F087120098; Tue,  3 Sep 2019 14:17:36 -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 tcEZldUPe63E; Tue,  3 Sep 2019 14:17:35 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B555120052; Tue,  3 Sep 2019 14:17:35 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57680 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i5GB9-0001ak-Qc; Tue, 03 Sep 2019 14:17:33 -0700
To: Robert Moskowitz <rgm@htt-consult.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
References: <E1i5EwG-00014Q-GV@durif.tools.ietf.org> <1d7e7040-d294-a5e0-ddac-399bf84578bb@htt-consult.com>
Cc: rfc-markdown@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <e48065b9-7639-854c-5e00-c9e28cd62740@levkowetz.com>
Date: Tue, 3 Sep 2019 23:17:20 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1d7e7040-d294-a5e0-ddac-399bf84578bb@htt-consult.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xIMkHmPDKLoHb4lhBthCejigQpJv55Wpr"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org, rgm@htt-consult.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/Rn3a0iOj0aYyBUPExLsnzZRlUHc>
Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.26.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 21:17:36 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--xIMkHmPDKLoHb4lhBthCejigQpJv55Wpr
Content-Type: multipart/mixed; boundary="LTpoDggGHQol53lXGIPSpW7Nf5mWojiSK";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Robert Moskowitz <rgm@htt-consult.com>, xml2rfc-dev@ietf.org,
 xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-ID: <e48065b9-7639-854c-5e00-c9e28cd62740@levkowetz.com>
Subject: Re: [xml2rfc] New xml2rfc release: v2.26.0
References: <E1i5EwG-00014Q-GV@durif.tools.ietf.org>
 <1d7e7040-d294-a5e0-ddac-399bf84578bb@htt-consult.com>
In-Reply-To: <1d7e7040-d294-a5e0-ddac-399bf84578bb@htt-consult.com>

--LTpoDggGHQol53lXGIPSpW7Nf5mWojiSK
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Bob,

On 2019-09-03 22:55, Robert Moskowitz wrote:
>=20
>=20
> On 9/3/19 3:58 PM, Henrik Levkowetz wrote:
>> Hi,
>>
>> This is an automatic notification about a new xml2rfc release,
>> v2.26.0, generated when running the mkrelease script.
>>
>> Release notes:
>>
>> xml2rfc (2.26.0) ietf; urgency=3Dmedium
>>
>>
>>    * Fixed an issue with nested <ul> with emtpy=3D"true".
>>
>>
>=20
> Gee, I hope this is not the way it is spelled in the code...
>=20
> :)

 :-D



--LTpoDggGHQol53lXGIPSpW7Nf5mWojiSK--

--xIMkHmPDKLoHb4lhBthCejigQpJv55Wpr
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1u2GAACgkQTptXS4+7
Fxqmfg/+MICYIoAyFWUP5OJw+KvfyEWopE20PH3S3RJCp6fywzp19DjeCSYSxGJE
DNVV7NDmR7Eefb5YeDo3zteLSrwL5g6vRG+C25ysOdef5e2BCaHbkXvE2ohVuEhy
5ecTdDM9WvarkcW2QY+6Hu/Eq5iosKhzWSyBkLbXxlhtsk1lAwECmfLMD0259mqI
C+TjbI+4DfYE090pRP3Hlz7uJ4EntEsaVyir65GmKqeGOqtEUl+kmSASya9mt24S
n6xVPPUnc/kKQR+yYVhbB6u11RKZwXFBcKzlDl0RzwESUue4rzCmS34S1dccpexi
AgppQWw77G/vvtgwcdx0SatD2rVY930Hmhhwl+dy+MOlSZM0o7EyYrB6mDabvBQr
fQEhbDeYqxwj2xpKI+akRa9Cji9VUN0gr3hP5u1I2cmwLA5em2cbo98WU9NOinYD
JtWBHir4LdT602r0cBXuw3gXMb8WzUrZvPx+a2IPrRHMj7hwZlMHDgn6mNlGlv1u
R1vKNIjACDxrij80GADF0RdCxKKnzU++Nn5K61INrQlrsTGzeMypM0yMZ9Uf77c3
4gqm/OGkyo7v4MuBQfZqyW7NTdRKuazVq16GSpSfWECXW/T960y/qg2M2dmt3S4y
GgElmvCSkt+eCYq5xH/s3SUhyYwMjC7O/0cc3nRpj7ik/J+Ecyw=
=H4Rx
-----END PGP SIGNATURE-----

--xIMkHmPDKLoHb4lhBthCejigQpJv55Wpr--


From nobody Mon Sep  9 10:04:18 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 291EB120853; Mon,  9 Sep 2019 10:04:14 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 hWZFvwGnHHGm; Mon,  9 Sep 2019 10:04:12 -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 0870312084D; Mon,  9 Sep 2019 10:04:12 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i7N5H-0002eM-SS; Mon, 09 Sep 2019 10:04:11 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1i7N5H-0002eM-SS@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Mon, 09 Sep 2019 10:04:11 -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/xml2rfc-dev/uHuAynw5hi6UslWZPrqPNJy_0Rw>
Subject: [xml2rfc-dev] New xml2rfc release: v2.27.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 17:04:18 -0000

Hi,

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

Release notes:

xml2rfc (2.27.0) ietf; urgency=medium

  * Added a test for handling of &wj; and &nbsp; during text linebreaking.

  * Corrected the line break handling for &wj; and &zwsp; and changed to
    using a unicode private use code for internal "don't break" handling,
    in order to make use of &wj; possible in the XML source input.

  * Added country name aliases for South Korea.

  * In text renderer: Reverted 'Internet Draft' to 'Internet-Draft' for
    series name rendering.  Stripped empty parts from Updates: and
    Obsoletes: lists.  Added removal of U+2060 (word joiner) before
    emitting rendered text.

  * Adjusted the preptool inserted reference target value for 
    Internet-Drafts to include a trailing '.txt' to avoid 404s

  * Added U+2060 (word joiner) to the list of code points that should not
    trigger non-ASCII warnings

  * Added an --id-is-work-in-progress switch to let the RPC automatically
    add a <refcontent> element indicating "Work in Progress" for
    Internet-Drafts.

  * In HTML output, removed blank items from Updates and Obsoletes lists, 
    and reverted 'Internet Draft' in reference rendering to 'Internet-Draft'.

  * Added entity definitions for &wj; and &zwsp;

  * Fixed pyflakes issue; a variable name mismatch.

  * Updated the installation instructions emitted when --pdf is specified 
    without having the necessary libraries in place to also include 
    instructions for Noto font installation.

  * Fixed an issue with the ToC generation where sections without numbers 
    might still be rendered with the whitespace intended to go between number 
    and section title.

  * Fixed an issue with the HTML ToC where sections without numbers might 
    still be rendered with the whitespace intended to go between number and 
    section title.

  * Removed pilcrows from print layout to avoid spurious extra lines for 
    paragraphs where the pilcrow would not fit at the end of the last line.

  * Fixed an insufficient test for URL vs. local file when handling the 
    --metadata-js-url switch.

  * Tweaked the CSS for print to avoid reference entries beginning on a new 
    line, below the reference tag.

 -- Henrik Levkowetz <henrik@levkowetz.com>  09 Sep 2019 15:07:36 +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.27.0'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Tue Sep 10 08:47:52 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFF1A1201DC; Tue, 10 Sep 2019 08:47:43 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 CmVXlTZlPxjY; Tue, 10 Sep 2019 08:47:42 -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 2DF80120043; Tue, 10 Sep 2019 08:47:42 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i7iMo-0000so-0z; Tue, 10 Sep 2019 08:47:42 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1i7iMo-0000so-0z@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Tue, 10 Sep 2019 08:47:42 -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/xml2rfc-dev/Q3hQEeq72I45YLcptQ6mKy0Wmy4>
Subject: [xml2rfc-dev] New xml2rfc release: v2.27.1
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2019 15:47:44 -0000

Hi,

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

Release notes:

xml2rfc (2.27.1) ietf; urgency=medium

  * Refined the preptool code that inserts reference target URLs to use an
    more appropriate guess at the extension, depending on the base URL.

  * Corrected a mismatch between the default value for a switch in run.py
    and base.py.

  * Changed the code for the --id-is-work-in-progress to avoid duplicate 
    <refcontent> insertion.

 -- Henrik Levkowetz <henrik@levkowetz.com>  10 Sep 2019 15:43:47 +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.27.1'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Sun Sep 15 13:23:20 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8F12120043; Sun, 15 Sep 2019 13:23:06 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ZiPcPsqO65e9; Sun, 15 Sep 2019 13:23:05 -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 4B53012002F; Sun, 15 Sep 2019 13:23:05 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i9b33-0000iJ-5e; Sun, 15 Sep 2019 13:23:05 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1i9b33-0000iJ-5e@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Sun, 15 Sep 2019 13:23:05 -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/xml2rfc-dev/QWE7D3WitlqmPPW97sjvQxEdWcM>
Subject: [xml2rfc-dev] New xml2rfc release: v2.28.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Sep 2019 20:23:07 -0000

Hi,

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

Release notes:

xml2rfc (2.28.0) ietf; urgency=medium

  * Fixed the handling of empty <workgroup> entries when writing HTML, and 
    added handling for multiple <workgroup> entries for text output.  Fixes 
    issue #425.

  * Fixed an inconsistency in the handling of non-ASCII author initials.

  * Added some XML cleanup before writing prepped output.

  * Fixed a case where for instance 'Section b.2' would be emitted instead 
    of the correct 'Appendix B.2'

  * Changed the restricted right margin for <dt> terms.

  * Added a check for conflicting schema information for v3 input files, 
    and fixed a failure to heed the presence of preptool errors when genreating 
    v3 format outputs.

  * Adjusted the library call default value for --legacy-date-format to
    match the command line setting.

  * Added a script to minify javascript (through an external service), and 
    added a javascript minification step to the Makefile.

  * Added a html <div> for external metadata, and updated metadata.js to 
    look for online metadata also for documents served from disk.

  * Fixed a problem with authors without any name, with only organization 
    information present.

 -- Henrik Levkowetz <henrik@levkowetz.com>  15 Sep 2019 20:16:05 +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.28.0'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Sun Sep 15 21:24:13 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9284F1201E5; Sun, 15 Sep 2019 21:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 VpHKLTHCK5Td; Sun, 15 Sep 2019 21:23:54 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C755912008D; Sun, 15 Sep 2019 21:23:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1568607813; bh=p7HSoP6GPgnkCMZLwnlFDgum6AbXFixRVczW3BSutVk=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=HSV0FuGAU/IF1DppSpdBhOeDjjPQ5AuSJoDaWD3OZ2kB8hVID1ooA2AL79JNhfpsv IK5382+nlJGFKq9OoMvXHgP+b5oN6QywWmqS+65tTDtUGaytTm4ee+wHS6+6bhZqeV 6oLgtJYnuDJHkt8UNB5PsSLZmpqsHuoev5oIiwHo=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.141.216]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MUHbK-1his0V2pNK-00Qx7B; Mon, 16 Sep 2019 06:23:33 +0200
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1i9b33-0000iJ-5e@durif.tools.ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <44fe97cd-6e97-1649-5ead-72521124e921@gmx.de>
Date: Mon, 16 Sep 2019 06:23:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <E1i9b33-0000iJ-5e@durif.tools.ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:4BRjC8hDI2gQ3aNblX7bgBQTCptOu0Py8Oe50pB3IwSXhDE8RTU UKb3fwyT5nrJ26IlEyrvP66/sHI1XJdEe4NYvXz9gXsO7fiN8pUodIOZKUfv7QwOZ6UAc5U eiIv/T1Lmsq7GThJ8uL6SJvMO5jbkfB3BtqvZb0ljyj3HTCQ27/XbP97RiJU8Ik+iSXkChe gZwL4TP1Iy5xqCoNHDbdQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:/IuSlEhTPss=:nH8UddTgB7JQ3FXL3SAKh7 T4GOzx7njwPKGnQN8NgTJSezayTn0EtRy6CWF5+g8uAluSeIU3f8rUbYcuehA5wrrPNYOnB7/ c32+yKYhyXzUztz1DDt0lqyB+ZoSFwAVNRqyH8JcBp1CWGLgMw4CV7nLGnoVvJ9NPdFcvg/5u SYhe1KQV4eg2TXVjbqKooQSVxu9Wfbjp2K40ewJNy3iUc8cogEKRooPPgnO9i+V2p3lYbAcrF 09o/zjwfbQbG6dBITYwqx7Srzm1k+Ttq9N73SHt0rV/PI/t69UJsJoE6aE7kXtjONJ4qXuRvP jHZTDDtnp4oojC67Lm/SyMwW4oAYzneD26rQcioXcf9uF/V41Ff1PaZS+89E3gccSXH9ixDn/ 2IC83V5rUzPEVdDMltpOoYRIqdy8ckjK6+ohT3jH5u1i/3/JbaqJ0O/+GJZPP6nzajd1R0zfm /x6Jt4CdGk59ml2yiHjcGoguyLpBCWIHLMyTbQpMlFA5uyyYOgf+IX3xaVb6V+cnkBjURj7QP nQGhmFQz7q8fQwTVbdrumI35KD5TSAcB21i3xcCIR43fUmVwIbobRNHriqAaD5RJ07Y/xBUO9 k5nKAeZA62T7rQzVBbxuIlxkql63YKMeMRe5JD6D1UYjcnm4Ra8FQRtYAfmQrAWGzBYrtXW1o kVeH9kJEoWaXbweRTAkWopA4wpA+qDiRNYbll2KKFvtM+XBr60MWdFOGteLL5Agcm2Xc8Ln+i BQfRy1OonizPOEw/miXMpTEIXl32Bsjg3LAQmHM3NCWn5D3q1S7Ef9lJ8oR6+w+o6CfD+AZpc 0pvU1nyoB44AoB9coZMiCJOX+YnESvroVuCcYFvgfHP2KiSG1OXShesX1LpL1ocVcDIeyb67U sYXPAp7166/znTstmMAvhHNXYj8WPrjJZga64aCOKznrCYA2LbX7dAyMsqS21s8dQgLO1YuJf rNUwmqpz7Z4U9fQ+8WmbjRPxIJX3THWiV8fXBelDeKufwIaVW7d6OJBBrZ4o6MS/3hD74TopS TZjG9vUWFkQzjGHxrfgw7xPr6/eTBC8OtytyPMynUyk5hJeD6K8MalAoDR9/fU/OSTl8kAUTa pDkXjLCDgTHxrguB291/OsLAIHQjYcFX05tiK6kqA+E7MbsHRc7Zy6T/ZpLIMRDqLiXIZYMFG wP+7Xv0mbvi93W+CQE/H+9hl/ZY3GzJ9Pil93utOHoh783/HKOC4E5RPtLSmnRNq2Qt9nQjB7 VhHe3qzhUzNCZT/7dFlXQGxVzHpGsXAO8H4McZhzNb/NoguUpfJfzlFmvAkQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/NJwnAxJXgnuMuYqRyd_eaGR0faI>
Subject: [xml2rfc-dev] multiple <workgroup> elements, was: New xml2rfc release: v2.28.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 04:23:57 -0000

On 15.09.2019 22:23, Henrik Levkowetz wrote:
> ...
>    * Fixed the handling of empty <workgroup> entries when writing HTML, =
and
>      added handling for multiple <workgroup> entries for text output.  F=
ixes
>      issue #425.
> ...

Interesting. Have you ever seen multiple <workgroup> elements in the wild?

I opened
<https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/99>,
proposing to tighten the grammar instead.

Best regards, Julian


From nobody Tue Sep 17 14:15:41 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F8A12007A; Tue, 17 Sep 2019 14:15:26 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 go3C1zf7Jizw; Tue, 17 Sep 2019 14:15:23 -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 580C1120043; Tue, 17 Sep 2019 14:15:23 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iAKol-0003df-02; Tue, 17 Sep 2019 14:15:23 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1iAKol-0003df-02@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Tue, 17 Sep 2019 14:15:22 -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/xml2rfc-dev/f9YqhxaoEB6AONyowT_gR2_h9uQ>
Subject: [xml2rfc-dev] New xml2rfc release: v2.29.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 21:15:26 -0000

Hi,

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

Release notes:

xml2rfc (2.29.0) ietf; urgency=medium

  * Adjusted the handling of ASCII, Latin, and non-Latin names and
    abbreviation in the v3 text formatter to act the same way as the v3
    HTML formatter.

  * Added RFC #### to the HTML rendered document title (for RFCs).

  * Added <artset> in the schema in two places that were missed when 
    first introducing it.

  * Changed the metadata json URL to avoid CORS issues due to redirects.
    Added a missing JS 'var' keyword and fixed a typo.

  * Handled a file open mode deprecation issue.  Fixes issue #427.

  * Added 'table' to the internal list of block-level elements.

  * Added the traditional default 'Network Working Group' to the top of 
    HTML output for drafts.

 -- Henrik Levkowetz <henrik@levkowetz.com>  17 Sep 2019 21:06:37 +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.29.0'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Tue Sep 17 21:32:28 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8091208B0 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 17 Sep 2019 21:32:27 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 P02h8NOfVxWR for <xml2rfc-dev@ietfa.amsl.com>; Tue, 17 Sep 2019 21:32:24 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5DE812006E for <xml2rfc-dev@ietf.org>; Tue, 17 Sep 2019 21:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1568781138; bh=vlSZ0a7RarN2UvbnBQH4eDQ4xZymEt/kiGHuBp6nju8=; h=X-UI-Sender-Class:Subject:From:To:References:Cc:Date:In-Reply-To; b=RwkpcguvJtLvpHWsZtJt0sCEkQ0Z3GKBSoySS8xUD1I+9+9XYAmL25vmzvidUdKd/ O7wboS9WRmMDfnXvaj0KH7fmPwyyAmav8t5my05/hqmHJSl5DdPW1KKUCL6CsHTqlu Ow4ncISekWr0abPbIOdxU3JHtaNt11LZTMPiNa/8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.136.221]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MOfcU-1iGTmJ3u5O-0064VU; Wed, 18 Sep 2019 06:32:17 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: xml2rfc-dev@ietf.org
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de>
Cc: "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Message-ID: <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de>
Date: Wed, 18 Sep 2019 06:32:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:PJy6fiAoqv+6pNUsYbE8Mr3M53jQolZS3wIC8wjPOen/fBMWgFL Q4zGW8zQiJ2C1IXrHXZ/8eJmzWJIw4ry6XyU5x7TnOkNj37U3kHygRg5eTfmihkSeuTXY5M Y6fzhhzl3IxBUNHdYpLOtZfgTp8twCkLI6o/c9DL3xiVA18+BvLpeWrNXoEa7+Wcr8bQqKw glmrdr2dh51BXHvlR1dfA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:I68LkMLKMpE=:QZthFBLJlFg5BQ7mgw/Of4 kMhyV2LqPOb1YuDkW5P5pxJ/LcbCL6P4JRHtjFb15zB+Ve31laQ+SXkGkhaSJLjpfdEdYJdpk 8fgqR+w3qoe2lJbPtsyBf0Xh0Xm2iCZIwSEYqsbAaAzKDkNRVAotjQW97Xk/bNbGHeui84X9A QaqO/YwWJV2NXRemDwy7Q/vWlW3r3YdipCMG54MkxTLO0hxvxVAvWOnY3qnZx/IYZLFOjpC61 1VQK4kz9YbcO9HnWVqyb1iTGs9DebuLVn92lAYXVsObJcDM0bFWaObYXNIsdFs7HHumsV5a0f 39KVGvdyRYXSwkBWIerek8yRtq/WYxu8AhPzB2gIpfC0yLtTEamNt20kjcVaKZ6e1Ru2NxZGc yc9dHBUBVbwOkcOj9Zv35sD87OOt2oYNXNG1TwyNhX6+OyAljaPjjvEjoiwMzafs3C/lWLfY5 0ed7cplH4j1ie2yOI0Y7R6d6+sauWDvsJzpRlaPCZQ8Fyb51P23I+xEhNwO8VV/Ph3Czn9eSB kvX3XJth7eiBS9kgrpecVdCiEUHcNWleixNAD54w3eAxowJtE5zKv/IzRyHQJlzWLgiN82Edt Bnh0+4/9Mjecpj5fKdmeiSrO/auX6UWBlnjgS93c7+EE2oTV8bCuMOuo+ICq9JvQ97ZaoXVj2 Vj1OGpg18tVRULuU80T0KVIP9jByXXT+f0LArqE4sOGFtHH88sR/KMy3JfSZYHRRSvI5ub6Hp WJOrnG0Y08H+f4P78h6vvbkApxbZp4TCruIkXoxe/77IlYIGnJC75qHgH2QPFiNvEWJYE8pzq eHGeK15UimHpRhMvOxTS2wFOXi/KWA63ytTDKMQdPeMITf8jxD5MMXmmb4izYjp+x2Bt7dqew jPuXbjEbVUjO7nLlpPNXmg5NUu70XS8AOW9PwaQ5krKDqfCzQcwfX3S2fKlg5RIZGjr4GowVz 6Rha6pFZOMW5YFBIs6uO4LlASPFQBkGiDSJBvx8IAyO8kkIOSzCTGVjS5M2KL65P1iI/ydr/1 FKiKybCSRdYXP2PxxaH6jY5bICEBV11sDx5l6HR/SHTf2jVAlUQj2x+Kv8JRCGFiVTeiAxPwF OTx9QSXSLj8txXBRevfEhI3UJNk3ZbYZnIVLyJu+M6zqmDhznkFhgMDIvKpLsBFHHu5N6vGIO ASPYBSZVHTg9QEe92UJr9HY6e/WvDumTgqGfpxUbCmWWqXm6lu/CtuPdeec7GPkffXHUnX1IL lBbk7O+Z9pyMXAnNJLwTbp+GsU0Wsw/1XKio7C859/ptY04z8MkbRb7R5wJI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/Grw1a6WmQYMKfP9t7tJMNLUpreE>
Subject: [xml2rfc-dev] RFC 8661 in AUTH48, was:  [v3] Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 04:32:27 -0000

On 03.08.2019 14:51, Julian Reschke wrote:
> ... >
>> ... >> The contributors section in both documents looks terrible in HTM=
L.
> Probably because there is no defined way to add contributors in a way
> that renders in a manner consistent with authors in text formats, so the
> authors choose to use <pre>/<artwork> for that section.=C2=A0 We need to=
 fix
> that somehow.
>>
>> Right - that was the only way we could get the info to display similar
>> to Authors=E2=80=99 Addresses.
>> We will discuss this.
>
> Please discuss here:
> <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/81>
> ...

FWIW, RFC 8661 (in AUTH48) has that problem.

Would be good to resolve it in some way before publication.

Best regards, Julian


From nobody Tue Sep 17 22:14:08 2019
Return-Path: <mt@lowentropy.net>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3195C12006D for <xml2rfc-dev@ietfa.amsl.com>; Tue, 17 Sep 2019 22:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=wi9Ft7hf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=EuvzDGgl
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 G17UNy0kaVDv for <xml2rfc-dev@ietfa.amsl.com>; Tue, 17 Sep 2019 22:14:05 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54FF51200E7 for <xml2rfc-dev@ietf.org>; Tue, 17 Sep 2019 22:14:05 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id A7391489 for <xml2rfc-dev@ietf.org>; Wed, 18 Sep 2019 01:14:04 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Wed, 18 Sep 2019 01:14:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=AuT8sCzWomziZhUUCXwCtB+K18MgZqN 98GbV8Gw6pCg=; b=wi9Ft7hfKQukKDKroGXrT1iH2683Fwxlff/+WXT2OCqqV2j QfFu/N3YAuW2/x8dxBTO7P/caIEFF1zAJaUi57vg5gAEaWqCOLgI8eYf4A5/iaB/ aFGqpiqOHDYzTeXTMfQwWkFc8KWxaRkXnuSKdAZ9UqOGh0tbgT+YlH3IdynHS2bL QR17X24QzSXbboacG2MMDudulymCdEPTabLV4eu4EaAc7LenIC6DGUaiYCLH+sHu f5p+puGbSvu5uasKr3qbHz43dyL1Z1GFArl1Lr6nmFSSBsKywKheMI64x4kKdFKq ZxSP2XIxlr29o5HzxwALEkDaIF5TL82PzuI6RPQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=AuT8sC zWomziZhUUCXwCtB+K18MgZqN98GbV8Gw6pCg=; b=EuvzDGglh/TqWKsRPjEdwa f4c3cPmO24N7ZkHLeIAdbzAcexPNB8xpgjnptNXCE651IbDKxT15T90n/vw7HMbz VD8sbzLFRw9Z2z9kp4ase12rOEpkXI/6pGITfTUzjRppmSttkBbpLEn0FazZb5mD iu2XfuZCOE75risCRDKHEzWZimjZKJOFovjV88uALPcv90Di82qZhgXLQHn/HKMY JU0kvDK9SSL0SsJjjx5hxWVpwhz/QFML2/puwEmpeel1xdZG+83sobK8o47Pzxit tlVsUbb9fFPru58EpOj8ZZVuL5VL5pPoovkPKygHp+pQj65PRD6Avcj2a9v6gpDg ==
X-ME-Sender: <xms:HL2BXUiWqz_p8N2-Xe_ha1VP5rhEpDDdsupcrBpyp6ahOyQGip5yCA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejgdelgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfrrghrrg hmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvthenucevlhhushht vghrufhiiigvpedt
X-ME-Proxy: <xmx:HL2BXVJ-cmqMmBgnmLDjRGg_L1WW4thh5_5Q1PrEuXmh1-d2ZMyrqg> <xmx:HL2BXbmCbokRXzIG9ERpR7LFkohds8nBqycp3LK_OM8Ca4e3xFM1WA> <xmx:HL2BXVNddhB5MPZiL2xHA_Rap22Psp9NpRQ5ha_kQUoddZyniiEMwA> <xmx:HL2BXY6b-nN3gdT_qbeoO4VM0Eu3IiXZ-xFTQrwz_8J3AfV0II-VgA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id DF0AB1C0001; Wed, 18 Sep 2019 01:14:03 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-238-g170a812-fmstable-20190913v1
Mime-Version: 1.0
Message-Id: <38e3f48c-a43a-4791-8449-ef7634d765e0@www.fastmail.com>
In-Reply-To: <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de>
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de> <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de>
Date: Wed, 18 Sep 2019 15:13:45 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: xml2rfc-dev@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/2DKAbslEypL-i_0KTx1FSloi-88>
Subject: [xml2rfc-dev] =?utf-8?b?PT9VVEYtOD9RP1JlOl9fUkZDXzg2NjFfaW5fQVVU?= =?utf-8?b?SDQ4LCBfd2FzOl9fW3YzXV9QbGVhc2VfaGVscF9yPz0gZXZpZXcgdjMgZmls?= =?utf-8?q?es?=
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 05:14:07 -0000

On Wed, Sep 18, 2019, at 14:32, Julian Reschke wrote:
> FWIW, RFC 8661 (in AUTH48) has that problem.
> 
> Would be good to resolve it in some way before publication.

I would love to have a resolution to this.  I don't see why we can't just copy the author bits and rename some higher-level elements to get this.  I want to style authors and contributors using similar methods.

For instance, two columns would be ideal for something like this: https://tools.ietf.org/html/rfc8446#page-153


From nobody Tue Sep 17 23:23:06 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08BB01200A4 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 17 Sep 2019 23:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 XbpyX3dH9KET for <xml2rfc-dev@ietfa.amsl.com>; Tue, 17 Sep 2019 23:23:02 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B75791201AA for <xml2rfc-dev@ietf.org>; Tue, 17 Sep 2019 23:23:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1568787771; bh=y5K9w2xw9rELMeJGcfzO85fvG2GFMWXgjNyWVY9iRBE=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=Hs+yT4mxual2qTpyb7wHZnRn56K7YOrqEy/ykhwik6vnKO0t97RQOT8rp6/x6aW5O JaxI5+Y5SzGwz5LknobwDmGHJgRGAkGvbvH9Tzfq4Xghf5mJnWm6WsdDkOndC/aUDc 0mWbDIR7KJH262na9d8BsT44bq8vY0K8GP0Y2Qck=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.136.221]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MWzfv-1ihAWI3OPZ-00XJig; Wed, 18 Sep 2019 08:22:51 +0200
To: Martin Thomson <mt@lowentropy.net>, xml2rfc-dev@ietf.org
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de> <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de> <38e3f48c-a43a-4791-8449-ef7634d765e0@www.fastmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <b2134087-071d-d8bf-484d-d6ad74dc318d@gmx.de>
Date: Wed, 18 Sep 2019 08:22:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <38e3f48c-a43a-4791-8449-ef7634d765e0@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:U5yN3yZ0XlJdXymsvRtxiUqPSmej3NpD+o4GKKQoPvvDlcN8/I5 cQfRrur8jefzIl7yPt+4ynP2sOfeW0akflKZsT/KmjN+KWK4/pSmQVwlVgqorZ/1EewP1eu v9ei0uKhPNsp8zUEyuES5CKZWMg5pWzAriJkBzyke0Cq4M0uKKjEGPfZNWdSKDJbWPUo8Oj OgvackljuNnTX/Rn7slsA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:LACMvDhem0s=:16HD1aRKumU1mmLFrAqWfi OajjyaQjlQDGT/qZVR7PYWB/boH1rvu6+HJenVaUtz8QC0smDEY3pOJ14naWyIWcQiRGGHKVi GSZ6U/A9XUtQ6/RwasZHempfEBhH8aKTaTDKUt5I94V0ifnr8GIwm1YoRUj0NkImNFbrLy+f4 mVMVcuk4Q1AIAyJAM8XEeahRCVLhF2ZRqgxoR+ozwpkR+OW/MZW7o9auIqbIS37apd6ClE7pW PxFoiryg4WEXY9yMMi1bx2lwkL7HTHCQoT24Ngfe5RSFIfC5aQdPjW82erAmwLmn0dG05PGNB 6YZHHFwiDhgHm9JtPYviH/P2Cqq7w9Di4FwbzHKKyAmc9P9Y2d9f/W0cOaBMTK1NPvcLnr5et CeIk+LokVkl9p+haLqwHWAmehxPn03gL1UJjYhexQt5yysDT9R9Ao6ltFICsRM+qr88sLEwv8 5LYIG6DqU9xlVMNXnaRBq+e8nAOkB36B868E5MuTM7JbJi1eRmVrlzNBBYVnVAwkuSOitWCb+ BOi0IA4PIrWSuNVZ0A/z6BOxEAfkht/ndcylpESHTYRmb4BFK1MsdHSZeqYgpaTaR3roVPj+O oMlbJ6RWQqEM9LrOi4Jrr45AcCfL6LGK7HH1Lve18ASfzadfU9b9UH7gCR3EFuVFSYhWbE50G KaywlLBPYFGIVrX3gG9AVUnpQHnYgeaeIctdLPJdoMj1cBRuUaz4QJXAyYyJzUNRAm74j3hWi AZ/DcY17ETNG0nrCLT1STIKoDVtHXKcY+8xLYH7jjRav6IyFVWDtGMcz+wtn9EG1XyNLce6VL ejTxAebQt/IAh2xp7QiuScC8zjSTgiPr7cxS+j6Hgx6KOmvtRid5gQjva+mBIyWf/famyHndr v2QkTcFdF/OXD2viOgv2ZEjy3xnOfGjv4qjbrvwrrhvYlUjmlDg8DBtF19HbM3RTUXb5Gt0uv 15+ES3tK5GuaKxKxFxW7Bvj5eIs6eZ5/WxEnB5MqpFwukgY4TLa+NQrYRFJTtzWR4QrVXL5L1 RBSTC1lIbs0W0zw0TfPAGOLFi9TAU7PQW51QNox19F0xYxRbqaFtU6MzzMIckyoejgQTD9BUv wcVCxlYC7H3XPgHuYsl4u5gkSBYABJPvNta7WyvYcDG0mkprDuhEXT93rx2FyQPYU7iVZIbBL NvJAz7G0JZriqLY5y9X8RIzdqJ/CrmkmKegv0ucOVn/A8oRuDr4gMWiXUkk7ZlHYOm+MG2nbF /If843oNM9x7TJPfJT7orh7ocnjSt8BUk7ETDl9Zw024Oszk7gnwvg7K7TiM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/7NEbcPxZRa4X9pYvkVJlB5wL2RA>
Subject: Re: [xml2rfc-dev] RFC 8661 in AUTH48, was: [v3] Please help r eview v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 06:23:05 -0000

On 18.09.2019 07:13, Martin Thomson wrote:
> On Wed, Sep 18, 2019, at 14:32, Julian Reschke wrote:
>> FWIW, RFC 8661 (in AUTH48) has that problem.
>>
>> Would be good to resolve it in some way before publication.
>
> I would love to have a resolution to this.  I don't see why we can't jus=
t copy the author bits and rename some higher-level elements to get this. =
 I want to style authors and contributors using similar methods.

I think a new element that can be used where <t> is allowed, and which
has exactly the same content model as <author> is the way to go.

See <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/81>
and
<https://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext.elemen=
t.contributor>.

> For instance, two columns would be ideal for something like this: https:=
//tools.ietf.org/html/rfc8446#page-153

Best regards, Julian


From nobody Wed Sep 18 08:24:33 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5F0D120890; Wed, 18 Sep 2019 08:24:20 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 cpnEyZ-P4Azx; Wed, 18 Sep 2019 08:24:19 -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 7B192120881; Wed, 18 Sep 2019 08:24:19 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iAboZ-0004HO-6y; Wed, 18 Sep 2019 08:24:19 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1iAboZ-0004HO-6y@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Wed, 18 Sep 2019 08:24:19 -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/xml2rfc-dev/ogCC8ISN8FSh8Up0RO8ATobtc5Q>
Subject: [xml2rfc-dev] New xml2rfc release: v2.29.1
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 15:24:21 -0000

Hi,

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

Release notes:

xml2rfc (2.29.1) ietf; urgency=medium

  * Fixed an issue with pagination that could occur if a table (or other 
    block) longer than a page ended on the last page.

 -- Henrik Levkowetz <henrik@levkowetz.com>  18 Sep 2019 15:22:19 +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.29.1'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Wed Sep 18 13:09:22 2019
Return-Path: <rse@rfc-editor.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A909120953 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 13:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 VOYziJ1U5VxN for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 13:09:18 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B50DE120086 for <xml2rfc-dev@ietf.org>; Wed, 18 Sep 2019 13:09:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A5729202192; Wed, 18 Sep 2019 13:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrFgB5BC_QNI; Wed, 18 Sep 2019 13:08:53 -0700 (PDT)
Received: from [10.15.85.93] (pppoe-72-19-47-021.cascadeaccess.com [72.19.47.21]) by c8a.amsl.com (Postfix) with ESMTPSA id 230B5202191; Wed, 18 Sep 2019 13:08:53 -0700 (PDT)
From: Heather Flanagan <rse@rfc-editor.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 18 Sep 2019 13:09:17 -0700
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de> <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>, XML Developer List <xml2rfc-dev@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
In-Reply-To: <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de>
Message-Id: <D7552A58-F10A-4600-962B-151DAB4DA6CB@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/ME7bvnJPfRNJ-6VRYfdejhUugRA>
Subject: Re: [xml2rfc-dev] [rfc-i] RFC 8661 in AUTH48, was:  [v3] Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 20:09:20 -0000

> On Sep 17, 2019, at 9:32 PM, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>=20
> On 03.08.2019 14:51, Julian Reschke wrote:
>> ... >
>>> ... >> The contributors section in both documents looks terrible in =
HTML.
>> Probably because there is no defined way to add contributors in a way
>> that renders in a manner consistent with authors in text formats, so =
the
>> authors choose to use <pre>/<artwork> for that section.  We need to =
fix
>> that somehow.
>>>=20
>>> Right - that was the only way we could get the info to display =
similar
>>> to Authors=E2=80=99 Addresses.
>>> We will discuss this.
>>=20
>> Please discuss here:
>> <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/81>
>> ...
>=20
> FWIW, RFC 8661 (in AUTH48) has that problem.
>=20
> Would be good to resolve it in some way before publication.

HI Julian, et al.,

The RFC Editor discussed this internally; we recognize it as a problem =
for more than just RFC-to-be 8661. That said, for now we=E2=80=99re =
going to use a work around, as the implementing of a new way of handling =
the role of =E2=80=9Ccontributor=E2=80=9D is outside the existing scope =
of work.=20

The plan for now is touse <artwork> element. Yes, it will look =
differently than Authors' Addresses in the HTML and PDF outputs. It is =
not ideal.

The future solution (TBD) may have us creating the role =
=E2=80=9Ccontributor=E2=80=9D and having that signal specific rendering =
details within the Contributor section.=20

This isn=E2=80=99t a showstopper for going live with v3.

-Heather


From nobody Wed Sep 18 13:22:43 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955C5120086 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 13:22:40 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 N6ICq1i3BtTf for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 13:22:37 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A429120046 for <xml2rfc-dev@ietf.org>; Wed, 18 Sep 2019 13:22:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1568838151; bh=sIlOQ9VAfSnH5OehVzDUq0Kfo3I4SGxJnLgPTwDrdzU=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=OqrfCgXhp73uTJQxrGS5x5alxByksVVb8I/K1zaAfeL7IXwOTAKR57YLeweUyh8QM MGaGFB8N6s+cS+gfH3dd+uMusZGhaOb3alFvNn2v1RLw5qjuWpC0E791Pr8ry8uzFu m7JcizrD7lfBYr4fbzTpaJ6aTXld8qTBsXF6rHPs=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.136.221]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N7zFZ-1i5xR62CeZ-0153Mg; Wed, 18 Sep 2019 22:22:31 +0200
To: Heather Flanagan <rse@rfc-editor.org>, XML Developer List <xml2rfc-dev@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de> <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de> <D7552A58-F10A-4600-962B-151DAB4DA6CB@rfc-editor.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <aa7f25f9-6568-5866-b3ae-bee1503dd59d@gmx.de>
Date: Wed, 18 Sep 2019 22:22:28 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <D7552A58-F10A-4600-962B-151DAB4DA6CB@rfc-editor.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:MVbtX178wSWZj4jZp8U3soVgLjY7RUm0EJoujWBM8+krOB+poMR EjG0FVgoLQ/S7ZE77PaFeneiSZp/ZkqF/cm2RSVt0XbJPmMm7IpzG3MsL3q1CjsHQnKaiyH kPRk8oVBfG5bJVuwPqxyhzoOCjpsotaPOW9Fmli7RmmOxVF+H8KEJK+TOkR+I1IaW5TWbxP 8xYH+YIsLpiN0ovrILNEA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:pKQAewDiCJ4=:+txiFosIPDZP+zFqhjMDH9 S75zcVowL5T4FfZC0hZrcHNTvAEmEYMYByZvXHMw7IkzDFKwtM/yBjpK1pPyDwjpcP+yuUzl0 qcxum5IEDmt5s4LB5n1BZX7Y6WZYWefCc+3sutPxyqEtSlDh2cL6QFrIL5AzJVL5gghUDBylP nBErxGDJmrf1RycmOC0YAVYBHLLTHk3JPQ9dE0IP3TbJnu/FBYiDAyaN/AqoXPQb4LfN4DwdI I739U01c/dWHuXBVZCa00C1oxK6J8VrD1KdpvsnlpvCVPDF6/DWqQTD/mfDToSh3ZO5TY96Qv 54DcH4TX4KyBXhzrs9nw6R6SC4Z9xKns9L9y+tF+t69BaQ253T8sjeSwEsz50d5wACWeCfXyh xnWqps7EXyQrA66W00Hqrh9G2TfyJ8qfvHUd/Eu3c1nCJEle/I0TDB3jqPjOS2VSRVKyN8k2U SCMmjiSavA5Q7VGFCsZDY5Cf5Wth1Y2cnE26gUD2I580eWw8/Vga4aDNOL59MfVHvuJHmyJ2Q QKx8V4C02Umtr/CVeTrToOcSmzEJ6hM1jziwobaJt/TfvDgqfkweEKt3ZcLF6oLxvg2Kuq2OZ ERBplxUZH0X+FkZBN8vKekVmxnDYpqNFqaWQcWIlD9Y6eVLSli5PYrDWQYrVFqLntNQIY9OlU vlAoULGFFt8wTDgzvZBOj9I6ElVX9/L/9LmiXz9fLGUVmhHkwDjKLnPbFOVOMLKPbvMTelRaX vVUGUPPWeQz2+2r0yaBaTci4pSAsTmWQoYgmpFevWuaK499QMabCU4YO40AHxHR7y2Bnrm0Ch u7sL7JRMCu2ZoGxGgKzcNaC6G8ozxh2FPSRfx9Iqtx3l5JFnsJ38YPFFei/kpMAUcGsb7KTga OZr1oi9Hx/Z68MfG2l9RzQko8umH52z/uPzaPt5ea4dAMpgoEX82Zf+sVNa8TgJGJLiZd2ktw X/l2baFK+H1xRRdl+pTkGzirhmzuWr9ZJ3af/JY1ccqNWK8x8AFvM+eXStxekcfCBC46ZBjVw z/qpbBIkHNoxoRvOobCSGpS9Tv7apNq9ZlfUd6sX8EoweZJOFXWh/C1HhRE0ypkqInn9XCrHb SIl+XSpjbidPfHKlDofuU7XOyMPr6uImjZBgHOy2ry/GnfX94T6opa4vNAxadV58HQNcAi360 CARUj/N4pal721ykCAEfqSCsykPTHe0zyBnci9x4IjPrP/EJO91NBOp3bae8I8VV8EzYBt9Xv nGGAGnJJUkXcQFrnelQF03E9wjttRFucD4D24gXsivlr2l32kx7Un2FQzYNA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/R_756i5CBEX_e8VC1BosL-9P0rw>
Subject: Re: [xml2rfc-dev] [rfc-i] RFC 8661 in AUTH48, was:  [v3] Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 20:22:41 -0000

On 18.09.2019 22:09, Heather Flanagan wrote:
> ...
>>
>> FWIW, RFC 8661 (in AUTH48) has that problem.
>>
>> Would be good to resolve it in some way before publication.
>
> HI Julian, et al.,
>
> The RFC Editor discussed this internally; we recognize it as a problem f=
or more than just RFC-to-be 8661. That said, for now we=E2=80=99re going t=
o use a work around, as the implementing of a new way of handling the role=
 of =E2=80=9Ccontributor=E2=80=9D is outside the existing scope of work.

Well, the issue has been known for several years now, so declaring it
out-of-scope is a bit weird. Note that this is a regression from v2,
where line breaks could be forced inside regular text, so at least no
abuse of <artwork> was needed.

> The plan for now is touse <artwork> element. Yes, it will look different=
ly than Authors' Addresses in the HTML and PDF outputs. It is not ideal.
>
> The future solution (TBD) may have us creating the role =E2=80=9Ccontrib=
utor=E2=80=9D and having that signal specific rendering details within the=
 Contributor section.

As discussed in the ticket
(<https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/81>),
adding a new role will not work, as:

- existing tools will treat contributors as authors, which they are not
- it does not address the RFC style guide suggestion to allow mixing
prose with contact information.

> This isn=E2=80=99t a showstopper for going live with v3.
>
> -Heather

Best regards, Julian


From nobody Wed Sep 18 14:04:37 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB94D120052 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 14:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 PNvRDpvyWSiC for <xml2rfc-dev@ietfa.amsl.com>; Wed, 18 Sep 2019 14:04:33 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 458B8120046 for <xml2rfc-dev@ietf.org>; Wed, 18 Sep 2019 14:04:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1568840670; bh=9/73S0F1gSUExphecIruqapv967a+mvuqdI5C2HIhRA=; h=X-UI-Sender-Class:Subject:From:To:References:Date:In-Reply-To; b=GwCxQfuhyltk7EVGCRaofo9X3WIQnnKZXt3GuZ+ghfmBVVIn+a1at/kfTgHK6bLiI YEkEaGe/F+YBG4aFyUQbevxbCpVrrQarCDIHmtHprKV3rICq/vadvCmJFPwNyXEXZu H1wr4i18EFxmmtFPELSc9KvL4hJA5qFZLSD9AYDk=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.136.221]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LsChr-1i4sWl1JB1-013wNv; Wed, 18 Sep 2019 22:59:20 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: Heather Flanagan <rse@rfc-editor.org>, XML Developer List <xml2rfc-dev@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de> <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de> <D7552A58-F10A-4600-962B-151DAB4DA6CB@rfc-editor.org> <aa7f25f9-6568-5866-b3ae-bee1503dd59d@gmx.de>
Message-ID: <a4e67a2b-90f8-bcc5-8139-1460064dc96f@gmx.de>
Date: Wed, 18 Sep 2019 22:59:17 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <aa7f25f9-6568-5866-b3ae-bee1503dd59d@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:15jZoOsCl26xpnchHQLP+joAZMvQGYMWXf1FvuyqerD5wXnpOhK e0dxx0LvEVAZa4Uyd2olah73ybpP3WpIoIeD5J2UUGtMV8KUInqM6BWalOTkagLggi5uvD4 fy39xfIy+M9xzYQp+bwNoRMSJnKThaKODDWAkTPY/VgAyfj3yzjzjZVuYdjC4CmedxebOAy vBr0Fj+Iq5Cgf5GFfqSBA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:yFLIEM0eIKY=:JJ6tYlvKW7ZhXOKBIquvyp WFNKJl8vXDT4WVer6oibWzYTq6Qe3bU+InwB1D0P/dhIKfhK6frfBM/NOi78y45Tt5Lt9DZ8w dQ+F2x+1ktwVn1+XtnJ/qPLf4T+yEdpLQdeUlg+yxQ1vrVoYctDWXrDqBe0sghdQsTJwoEhzv tG65C+sBC/isMcxGHrmOTejhb/BQtjUmIs7HnieaCM6McLCn/fWrFN/t9dI20McM/4zb36Tia VRZ+oC0yuFrzIO9O5iPY/xLKx4gLi+haFuN9+GnRDZEgz4yz+MdTPOqD5O/emvpBHcjoYYWP+ muAdazChNyZFS9K9GFC343/xdq8fNF9Cf2j41Xzc3nrCNuYIT1pBZg+RcPJAa6toA0vG6h5Fp RaUiOmJbZGVnG26UuqQBtNQYS4PFG8YIOsysSgTzkwXbF5BZFXX8T/2eQunNJ9OXjRO462s2t 1iyfw1V349QV/ZwYqDn+kVnnDhxYvvTvtRHHpWxHiceQD9mmOBawNpn4GaJMCqCrL0HbjY3Ri ZpkzQdYNZawNJzeHj0yCd/N+GyTPqAAGvJV3bipF4eGgzECsqf32xRldqENoYD3xbUL/J5qX/ 387HGN75HkPhGdgDqWSZZXT5nMwbeWb053/glXl75V0EuThKoZRkRcb5er/XfCTdJhHWKLqnv Ig7fuiwz0bluUAkDnNMDWvJwDyoMnF32keq6m57QtS3wwcRR2nt6hceJwgfd/0/tWUcKVuE/j v61MMKg7imlm341sDOyrHoxasJ58sr7YGxltNU9nv7EMFpTzKSB96s6WsLKKymXRzLC2Pv7JH hDg850DSZ7sJq2DvwV8IjkCY7CuVHEvwFH+YbMXFHRg4KrkbH/21BL4BYRDYnBjna71Kha2FD AYvXn/Xb9JYZWrMAmpbOM5DJCl2KdtikubCsvO6qom6TjpLNnQLtOFZ0/s3D7KwuH3WgodxV4 nYFVOGJVZO1xkzcAHcw2pbohbFeF83zbLbj03WBftdrdZhjk3CpS0WBRHIP+SXC6infn4oCSn VbCoNe93i2QqtW+Us+9s184lPGc6vchP0xGpyhfXLr1s+EJjezt2plIaWYGFgfI9wChV7GYf8 O+l3Jc8M6LKI3QBU5pjqI+21v8Lwb9yaqlAlm+7fsHrUuZDv18lrgmOT8saFzOT87W+dM16Vz RazFSXtnAIzpiUEWIu+6usr3xp76IrHjNz9P7LxYt68EVodFw5aZAFVjYCK7toLrSVoIwE+ze 8kiA2dpzO12TusB5UJZWQ9ur5TkgFt2mQQfBTN1Tvop5ch8Ob/rcH1M4rK5M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/vIH1ye3aZUIT-PrLmTbOFoOGzvU>
Subject: Re: [xml2rfc-dev] [rfc-i] RFC 8661 in AUTH48, was:  [v3] Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 21:04:36 -0000

On 18.09.2019 22:22, Julian Reschke wrote:
> On 18.09.2019 22:09, Heather Flanagan wrote:
>> ...
>>>
>>> FWIW, RFC 8661 (in AUTH48) has that problem.
>>>
>>> Would be good to resolve it in some way before publication.
>>
>> HI Julian, et al.,
>>
>> The RFC Editor discussed this internally; we recognize it as a problem
>> for more than just RFC-to-be 8661. That said, for now we=E2=80=99re goi=
ng to
>> use a work around, as the implementing of a new way of handling the
>> role of =E2=80=9Ccontributor=E2=80=9D is outside the existing scope of =
work.
>
> Well, the issue has been known for several years now, so declaring it
 > ...

16 years, apparently:
<https://mailarchive.ietf.org/arch/msg/xml2rfc/V6eiR3kzg3svDwJRPnh4st4K-Zs=
>.

Best regards, Julian


From nobody Thu Sep 19 02:35:48 2019
Return-Path: <sm@elandsys.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DEE41208FE for <xml2rfc-dev@ietfa.amsl.com>; Thu, 19 Sep 2019 02:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 LMDpWaefMjqQ for <xml2rfc-dev@ietfa.amsl.com>; Thu, 19 Sep 2019 02:35:45 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 930CC1200F8 for <xml2rfc-dev@ietf.org>; Thu, 19 Sep 2019 02:35:39 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.140.165]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x8J9ZMWX027600 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Sep 2019 02:35:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1568885736; x=1568972136; i=@elandsys.com; bh=/zui4M2QGwAdYGPJRx0dARM8LwSEN5QdJt8lh29PXcE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fih0fGG+SBw71nsL+ixbbGZifv1HlfPaWn2QXkcjASB6wyj3G9TxqZzGB3yOqJLzt JxollqJTV1airjoaBch7SXy60u8fatL6e8o/Yb7cBFAyB+MiWogUvr4fvd2U1rbX5T 25qwmgC/Vxv4V/KEVK1ZaFzUPha90J4RxrIiPMuU=
Message-Id: <6.2.5.6.2.20190919023037.0bfb9c68@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 19 Sep 2019 02:35:08 -0700
To: xml2rfc-dev@ietf.org, rfc-interest@rfc-editor.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, Heather Flanagan <rse@rfc-editor.org>
In-Reply-To: <aa7f25f9-6568-5866-b3ae-bee1503dd59d@gmx.de>
References: <6D7CF9A5-F8FA-4D78-9001-ADC7CD0B2A36@amsl.com> <6AFC0271-060C-4A2F-84EE-CB40DD328039@amsl.com> <eaf9e970-c570-4ee8-096c-ec70e85c4af5@gmx.de> <dabe2baa-9d71-0089-a486-844a3b24a08b@gmx.de> <D7552A58-F10A-4600-962B-151DAB4DA6CB@rfc-editor.org> <aa7f25f9-6568-5866-b3ae-bee1503dd59d@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/6nmsFLOfsdgjabzpdSl0RhVqruA>
Subject: Re: [xml2rfc-dev] [rfc-i] RFC 8661 in AUTH48, was:  [v3] Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2019 09:35:46 -0000

Hello,
At 01:22 PM 18-09-2019, Julian Reschke wrote:
>On 18.09.2019 22:09, Heather Flanagan wrote:
>
>>The RFC Editor discussed this internally; we recognize it as a 
>>problem for more than just RFC-to-be 8661. That said, for now we're 
>>going to use a work around, as the implementing of a new way of 
>>handling the role of 'contributor' is outside the existing scope of work.
>
>Well, the issue has been known for several years now, so declaring it
>out-of-scope is a bit weird. Note that this is a regression from v2,
>where line breaks could be forced inside regular text, so at least no
>abuse of <artwork> was needed.

Given that this is a known problem and it is not that new, why is 
outside the existing scope of work?

Regards,
S. Moonesamy 


From nobody Thu Sep 19 04:50:53 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6FDF1200E9; Thu, 19 Sep 2019 04:50:51 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 RuecEf6ENSh9; Thu, 19 Sep 2019 04:50:49 -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 CE96B12003F; Thu, 19 Sep 2019 04:50:49 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iAuxV-0002lQ-J2; Thu, 19 Sep 2019 04:50:49 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1iAuxV-0002lQ-J2@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Thu, 19 Sep 2019 04:50:49 -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/xml2rfc-dev/HoZ4tzvgukHi8Utc0WVL-mW3T6U>
Subject: [xml2rfc-dev] New xml2rfc release: v2.30.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2019 11:50:52 -0000

Hi,

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

Release notes:

xml2rfc (2.30.0) ietf; urgency=medium

  * Added logging configuration for weasyprint.  This controls the logging
    level based on the --quiet and --verbose flags, and should make
    weasyprint logging ouput more consistent across systems.

  * Weasyprint reports ERROR if a CSS <link> URL isn't available, so we
    won't insert a <link> for "rfc-local.css" when generating PDF if the
    file doesn't exist.

  * Tweaked the Makefile to use --add-include in some cases, for regression 
    testing.

  * Corrected the <xi:include> links produced during v2v3 conversion with
    the --add-xinclude switch, 

  * Changed the code to not retain <!ENTITY> declarations after v2v3
    conversion.

  * Changed BaseV3Writer.die() to raise an exception, rather than exit on 
    the spot, in order to do the right thing when called as a library.

  * Tweaked the command-line messages when a fatal error is raised in a 
    writer.

 -- Henrik Levkowetz <henrik@levkowetz.com>  19 Sep 2019 04:48:21 -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.30.0'

Regards,

	Henrik
	(via the mkrelease script)


From nobody Wed Sep 25 13:42:21 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ADAD120018; Wed, 25 Sep 2019 13:42:06 -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 LF5ptY0nYSCb; Wed, 25 Sep 2019 13:42:04 -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 B1A97120124; Wed, 25 Sep 2019 13:42:04 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iDE6u-0004WP-Ev; Wed, 25 Sep 2019 13:42:04 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1iDE6u-0004WP-Ev@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Wed, 25 Sep 2019 13:42:04 -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/xml2rfc-dev/GWmCDPccdYpJ6lNt1kZs7ZPb7Ao>
Subject: [xml2rfc-dev] New xml2rfc release: v2.31.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 20:42:07 -0000

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)


From nobody Wed Sep 25 13:57:12 2019
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F7651201E3; Wed, 25 Sep 2019 13:57:10 -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 d9BojBwNe-Qs; Wed, 25 Sep 2019 13:57:08 -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 3FF25120124; Wed, 25 Sep 2019 13:57:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 21F39615EB; Wed, 25 Sep 2019 16:57:07 -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 M9LB6qV35MOY; Wed, 25 Sep 2019 16:57:01 -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 3DE9260029; Wed, 25 Sep 2019 16:56:57 -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>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <445c7666-57bb-cb3b-f95e-e2186aea92a7@htt-consult.com>
Date: Wed, 25 Sep 2019 16:56:53 -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: <E1iDE6u-0004WP-Ev@durif.tools.ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/vS97Oj2BTFjh4xoTTyzWN82OmJ8>
Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.31.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 20:57:10 -0000

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

$ 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


From nobody Wed Sep 25 14:09:28 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0128A1207FD; Wed, 25 Sep 2019 14:09:17 -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 LWlvVHQAr_oM; Wed, 25 Sep 2019 14:09:15 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C156C12022C; Wed, 25 Sep 2019 14:09:15 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:52828 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iDEXC-0005Ec-Ni; Wed, 25 Sep 2019 14:09:15 -0700
To: Robert Moskowitz <rgm@htt-consult.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
References: <E1iDE6u-0004WP-Ev@durif.tools.ietf.org> <445c7666-57bb-cb3b-f95e-e2186aea92a7@htt-consult.com>
Cc: rfc-markdown@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <0b295bd9-8f2a-6eb9-bf04-911f5635aeab@levkowetz.com>
Date: Wed, 25 Sep 2019 23:09:06 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <445c7666-57bb-cb3b-f95e-e2186aea92a7@htt-consult.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UqOvv7TkHCdI9aSmqKo8IaeA4CsnHFVNu"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org, rgm@htt-consult.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/zsQ8_LThQ0Vwla5Spnok-ArApFA>
Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.31.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 21:09:18 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--UqOvv7TkHCdI9aSmqKo8IaeA4CsnHFVNu
Content-Type: multipart/mixed; boundary="lSrBoTnhW8BtGF7NMwhrL1xiDsrBodaK2";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Robert Moskowitz <rgm@htt-consult.com>, xml2rfc-dev@ietf.org,
 xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-ID: <0b295bd9-8f2a-6eb9-bf04-911f5635aeab@levkowetz.com>
Subject: Re: [xml2rfc] New xml2rfc release: v2.31.0
References: <E1iDE6u-0004WP-Ev@durif.tools.ietf.org>
 <445c7666-57bb-cb3b-f95e-e2186aea92a7@htt-consult.com>
In-Reply-To: <445c7666-57bb-cb3b-f95e-e2186aea92a7@htt-consult.com>

--lSrBoTnhW8BtGF7NMwhrL1xiDsrBodaK2
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Bob,

On 2019-09-25 22:56, Robert Moskowitz wrote:
> This does not fix my character problem (probably was not intended to do=
=20
> that):
>=20
> $ 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=3D'ASIACRYPT-2017' >
  <front>
    <title>Full-State Keyed Duplex with Built-In Multi-user Support</titl=
e>
    <author initials=3D"J." surname=3D"Daemen" fullname=3D"Joan Daemen">
      <organization></organization>
    </author>
    <author initials=3D"B." surname=3D"Mennink" fullname=3D"Bart Mennink"=
>
      <organization></organization>
    </author>
    <author initials=3D"G." surname=3D"Van Assche" fullname=3D"Gilles Van=
 Assche">
      <organization></organization>
    </author>
    <date year=3D"2017"/>
  </front>
  <seriesInfo name=3D"Advances in Cryptology - ASIACRYPT 2017" value=3D"p=
p. 606-637"/>
  <seriesInfo name=3D"DOI" value=3D"10.1007/978-3-319-70697-9_21"/>
</reference>

The more general solution (which isn't available immediately) is that the=

bibxml7 script is modified to transcode non-ASCII punctuation to ASCII
equivalents.

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


Regards,

	Henrik



>=20
> $ xml2rfc --version
> xml2rfc 2.31.0
>=20
>=20
> 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=3Dmedium
>>
>>    This release adds a feature to help with conditional line breaking
>>    inside table cells, and tweaks the layout of text in cells slightly=
=2E  It
>>    also fixes an incorrect line-break point and second-line indentatio=
n for
>>    long section titles in the v3 text formatter.  From the commit log:=

>>
>>    * Fixed an issue with leading and trailing space padding in table c=
ells,
>>      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 ti=
tles
>>      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=3DTru=
e when
>>      in the PdfWriter.
>>
>>   -- Henrik Levkowetz <henrik@levkowetz.com>  25 Sep 2019 13:38:34 -07=
00
>>
>> 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
>=20
>=20


--lSrBoTnhW8BtGF7NMwhrL1xiDsrBodaK2--

--UqOvv7TkHCdI9aSmqKo8IaeA4CsnHFVNu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl2L13IACgkQTptXS4+7
Fxr8rg//YQrfxXd9+Yh/4GqYL90LqiBUyScx50LCy91t6rcamHXOh/qksbqSjeRI
8EaSqWEEtvR9tdU2pUwWwWYPWf7lHNNHKJ+NLVCbHmc3Orqc64jBGnjhGB9av2D9
6QD0+mV/pxqAOsJrWAsI6fXjsjUL2HJG9QbchrNOqA/MUh8FLwafkd2g4D3NswwZ
K1TQIrrsCTkJrFEpykV0ZSE3MJ8DlNfYrB1unGLwQ1tEIXcC+j+cl3dmBEcUs2Gy
ssvV6wpMv7Nc5TYFYxiwFjJ9u2y4Qiej7ApzcFoSOG3FL/0fbtySF3oyLjDbMMr6
gPVBa/u1E1suDfb3GbIKuKSS1Mqt5OrFcEw4DOQGax8UyLCQRrj20/+8OM+opijR
7wqST282RMVXC/BrDlwgW/1yjJdFRaJ3FPIfIXfZx+IkY2/+DD30mNRTta078ZEq
yTiNKYlpdlyEyUUx/1m05aA1T9diJNdPVgj1tSponfx7uYNjVd3eTU4Tve2X7Ymx
j7hD31KRhCBzvLPFBtVEDlcEfSgoOThJF84C1ON4y2n2Mrn1SiAcfuqAqsalevj9
2Tx1DaI+TrTBmpmIuWzqACQDFil1VBwUa1qfuWw++92KRMf+WCgl4aYto9d63CTS
21vC1/L+A3/hnV3lclNHnd/qIVe2ry1Nn43QdVkgvoDzTyM6HBA=
=B75v
-----END PGP SIGNATURE-----

--UqOvv7TkHCdI9aSmqKo8IaeA4CsnHFVNu--


From nobody Wed Sep 25 14:32:07 2019
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@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/xml2rfc-dev/rf8op0PROp7ULlctEDAGCu3lyTw>
Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.31.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-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
>>


From nobody Wed Sep 25 14:54:49 2019
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08C58120804; Wed, 25 Sep 2019 14:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 WY4F-wVsbQpA; Wed, 25 Sep 2019 14:54:36 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 8D6B01200A4; Wed, 25 Sep 2019 14:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x8PLsLOS027488; Wed, 25 Sep 2019 23:54:26 +0200 (CEST)
Received: from [192.168.217.102] (p548DCE50.dip0.t-ipconnect.de [84.141.206.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 46dsK96B0pz1Bp8; Wed, 25 Sep 2019 23:54:21 +0200 (CEST)
Content-Type: multipart/alternative; boundary=Apple-Mail-282014A4-6050-4EA6-BDC5-11D901BB25CB
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <0b295bd9-8f2a-6eb9-bf04-911f5635aeab@levkowetz.com>
Date: Wed, 25 Sep 2019 23:54:21 +0200
Cc: Robert Moskowitz <rgm@htt-consult.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <1D90CB28-78B2-4521-9D69-EAE387296E4B@tzi.org>
References: <E1iDE6u-0004WP-Ev@durif.tools.ietf.org> <445c7666-57bb-cb3b-f95e-e2186aea92a7@htt-consult.com> <0b295bd9-8f2a-6eb9-bf04-911f5635aeab@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/sz650X1rB6eYCAx0SCOl8AqAMJU>
Subject: Re: [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.31.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 21:54:39 -0000

--Apple-Mail-282014A4-6050-4EA6-BDC5-11D901BB25CB
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

It sure should. That en-dash *is* part of the Seriesinfo, and if rfcxml deci=
des to be unreasonable about that, the tools should help (especially given t=
hat you already have the code to regress the body text into the last century=
).=20

Sent from mobile, sorry for terse

> On 25. Sep 2019, at 23:09, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>=20
>  I don't know, maybe it should.  Or maybe not.

--Apple-Mail-282014A4-6050-4EA6-BDC5-11D901BB25CB
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">It sure should. That en-dash *is* part of the Seriesinfo, and if rfcxml decides to be unreasonable about that, the tools should help (especially given that you already have the code to regress the body text into the last century).&nbsp;<br><br><div id="AppleMailSignature" dir="ltr">Sent from&nbsp;<span style="font-size: 13pt;">mobile, sorry for terse</span></div><div dir="ltr"><br>On 25. Sep 2019, at 23:09, Henrik Levkowetz &lt;<a href="mailto:henrik@levkowetz.com">henrik@levkowetz.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div dir="ltr">&nbsp;I don't know, maybe it should. &nbsp;Or maybe not.</div></blockquote></body></html>
--Apple-Mail-282014A4-6050-4EA6-BDC5-11D901BB25CB--

