IETF Logo Mail Archive

Re: [rfc-i] Update: The transition to xml2rfc v3 (today!) (fwd) Heather Flanagan: Update: The transition to xml2rfc v3 (today!)

Dave Rice <dave@dericed.com> Thu, 10 October 2019 15:01 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E2F1200DB for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 10 Oct 2019 08:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.949
X-Spam-Level:
X-Spam-Status: No, score=-4.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 GiFpHfQ94cYd for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 10 Oct 2019 08:01:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97FC312001A for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 10 Oct 2019 08:01:39 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D4202B80C60; Thu, 10 Oct 2019 08:01:29 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 28C89B80DA1 for <rfc-interest@rfc-editor.org>; Wed, 9 Oct 2019 08:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZhhtpRkmVtrC for <rfc-interest@rfc-editor.org>; Wed, 9 Oct 2019 08:32:50 -0700 (PDT)
Received: from server172-3.web-hosting.com (server172-3.web-hosting.com [68.65.122.111]) by rfc-editor.org (Postfix) with ESMTPS id C8526B80D9D for <rfc-interest@rfc-editor.org>; Wed, 9 Oct 2019 08:32:50 -0700 (PDT)
Received: from [146.96.19.240] (port=62377 helo=[10.10.201.23]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <dave@dericed.com>) id 1iIDxL-002Zuo-Lp; Wed, 09 Oct 2019 11:32:57 -0400
From: Dave Rice <dave@dericed.com>
Message-Id: <3650B5EF-A442-4291-928A-2FCB2144134C@dericed.com>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Wed, 09 Oct 2019 11:32:42 -0400
In-Reply-To: <3a8f5865-9f5c-8c65-63be-bca31c5f1c86@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <20285.1568652805@localhost> <705AA16B-68B1-4B5E-AE47-0714F6781C1A@dericed.com> <26105.1568818137@localhost> <E70CD0FF-0294-47E5-873F-5E184A248577@dericed.com> <1268.1568828850@localhost> <B4047303-E2B9-4B9D-B368-2ACC85A06D15@dericed.com> <15814.1569013442@localhost> <3a8f5865-9f5c-8c65-63be-bca31c5f1c86@levkowetz.com>
X-Mailer: Apple Mail (2.3445.104.8)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server172.web-hosting.com
X-AntiAbuse: Original Domain - rfc-editor.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dericed.com
X-Get-Message-Sender-Via: server172.web-hosting.com: authenticated_id: dave@dericed.com
X-Authenticated-Sender: server172.web-hosting.com: dave@dericed.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
X-Mailman-Approved-At: Thu, 10 Oct 2019 08:01:28 -0700
Subject: Re: [rfc-i] Update: The transition to xml2rfc v3 (today!) (fwd) Heather Flanagan: Update: The transition to xml2rfc v3 (today!)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest <rfc-interest@rfc-editor.org>, tools-discuss@ietf.org
Content-Type: multipart/mixed; boundary="===============7844767342245357904=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Thanks Henrik,

> On Sep 20, 2019, at 5:26 PM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> 
> Hi Michael, David,
> 
> On 2019-09-20 23:04, Michael Richardson wrote:
>> 
>> Dave Rice <dave@dericed.com> wrote:
>>> Another annoyance here is the the xml processor in the submission tool
>>> and the xml processor at
>>> https://xml2rfc.tools.ietf.org/experimental.html
>>> <https://xml2rfc.tools.ietf.org/experimental.html> perform differently,
>>> so there’s effectively no test environment to use before submitting.
>>> Dave
>> 
>> Dave, can you please try xml2rfc.ietf.org, which is a different installation,
>> supported by a different entity?
> 
> Michael:  Umm, no, that redirects to tools.ietf.org, too, and the processor
> behind that, and behind https://xml2rfc.tools.ietf.org/experimental.html,
> _and_ behind the submission tool are all the latest release of xml2rfc.
> 
> David: I'd be happy to look into any discrepancies you see, but I can only
> do so if you provide observations and input XML files for me to work
> with.  It won't happen if I don't know about it :-)

When I use the tool at https://xml2rfc.tools.ietf.org or https://xml2rfc.tools.ietf.org/experimental.html, the plain text output appears ok, but when I use https://datatracker.ietf.org/submit/ <https://datatracker.ietf.org/submit/>, the contents of the <sourcecode> elements (which are new in xml2rfc version 3) have their line breaks stripped out and thus cause an error when the line length limits are exceeded.

For the moment, I’m proposing a find and replace to convert the newer <sourcecode> elements back to <artwork> elements as in https://github.com/FFmpeg/FFV1/pull/171/commits/a018f091534678f45cc157bfd154518ad6267c7e <https://github.com/FFmpeg/FFV1/pull/171/commits/a018f091534678f45cc157bfd154518ad6267c7e>, thus an xml2rfc version 2 processor or version 3 processor should proceed accurate results though not as semantically clear in the xml.

> FWIW, if you have a tools.ietf.org login, you can use the xml2rfc issue
> tracker at https://trac.tools.ietf.org/tools/xml2rfc/trac/newticket, for
> xml2rfc issues, and https://trac.tools.ietf.org/tools/ietfdb/newticket
> for datatracker issues.

I don’t have a login, but I’ll see if I can make a tiny test file for this issue and file a concise ticket.
Dave
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email