[Tools-discuss] missing line ends in generated TXT (from datatracker)

Julian Reschke <julian.reschke@gmx.de> Fri, 25 October 2019 06:18 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E06F1200F8 for <tools-discuss@ietfa.amsl.com>; Thu, 24 Oct 2019 23:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 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, 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 JGHa_5BbzXTo for <tools-discuss@ietfa.amsl.com>; Thu, 24 Oct 2019 23:18:34 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 8E69512006F for <tools-discuss@ietf.org>; Thu, 24 Oct 2019 23:18:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1571984210; bh=wWsugAkn33tnso8AnyHZUUAKFqvV2hhsZEwSdEj9Ir8=; h=X-UI-Sender-Class:Subject:From:To:Cc:References:Date:In-Reply-To; b=QXYf9c0NwUfYS7W/RZQSWWNRY4/lkvZvGfZO+8zgnAtNpwMxRLgyL2baVj/vt/NFO 4UhClYcajpdM5WeDsog7sdxFjLp5fTc49NWRg3Ft4TBPGQydckWyXRd5RBYbN9M5w6 drDIWcwZxwz1tqiINiKT19NrwP11Rq2J138sxu+8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.151.92]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MgNct-1hnARJ1Bd9-00hune; Fri, 25 Oct 2019 08:16:50 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: Dave Rice <dave@dericed.com>, Henrik Levkowetz <henrik@levkowetz.com>
Cc: rfc-interest <rfc-interest@rfc-editor.org>, tools-discuss@ietf.org
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> <3650B5EF-A442-4291-928A-2FCB2144134C@dericed.com> <06122b6d-d5f9-30b9-2db4-a2427d299a1f@levkowetz.com> <CB32A50B-D6F2-41C4-8AC7-750E35F4941D@dericed.com> <97e68838-ac0c-25e4-67a9-a2a998b6e8af@gmx.de>
Message-ID: <3ef6a53c-e18a-9fc7-8324-67f388acd32f@gmx.de>
Date: Fri, 25 Oct 2019 08:16:45 +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: <97e68838-ac0c-25e4-67a9-a2a998b6e8af@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:MBnJAnVKOgM+sjCWIdFt2lyL84dXkIg63W5f9p0iG2MBbzzi6gk ey0/NMAsCmueR+gv8mgHF6XjYeKXz0OSsd9zHIrC4s1KX91ke1f7EdD71h1qT1eDZfkqdPG seHJVYVEYFKEMyKpeqObTJBBnyWOJBiqaIbhHAXFIcL4S+1j+jvqN3SaSS6zXzN9DwrI+lu 03e6ul0w6Oar6X5MinjsQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:om9Edv4WLmA=:93xq7t0leOVvFtWFw7qR3l OXKbHgt9PD437BXTm2/QZhFbBxIl/OwnOXfNl42k6u4ORZ3kZkfBbHw/991uH2QfAkpePJcP+ rxrQnu2fKlV48NCD6T8zZQX+gz8HlSVpcpo7sf0+H0DObxFEIwe3DEjw12U9rc8TGcpg1bqP4 fYFH2vRbgx73uhp3B3Gzesa1/G2kmf6L8Q84fgtuu4I/eTGfrT4XTJrDetLb12Qke4Z4re02M evo3mKL8pIqm88CjhkJcDyyzDOCqEgJ+6GkEZ2jLEBo4hyex0qdmNSZGOc2ICuD40gjBLYjaV 7+0+jDnfqWY+OaVeCRmzHjsSN2yXsBzKIjmc5Lb33v2ivBinULtntWJALBx3ic+QhASH5eWoT rOHfuNID5NA9mg/cNcd5q3wb/aFmtF/eTGsQus8j63nSobSec3QeUNuxNImDbtRrKUgNvJalb wywVj/f1T1q8CWEW2sQ3x+d+rHSSn36daqafxn6Jm3Pzxzsvsv7dN6JCDFSlIK2rFwOWVJN0F +0StPzomoLJ9cjx/zj8I4WOXfbanYCVMnL5Ymt4q2HzLe8hgOswTWttLpAvIuuvDflNqpQ0q+ ShdM3I3TkT72gMebPzhmMgGBMgaQoHAeRu0KK+CWd+sZnFyoB6IWwDZvc23tYIZ7Aq9TAynM/ H7AKt0R1+8SE4j6DVZwaz6c89X0LxsFqSnQDkseeDjB3BtqBbZ9K3QldZtm99KCyPpvVp+k5k hkhRdcr5JhKxoNpQGYrXeaYoYf5dmXGUOBIUXP2XWxQADdZAl7b37Qboskqq9HLidY86baW5X xoxoZoOmkmMl2Rc9UtVg6Y8m3WwnhfTq7xQv7H1Kk/zB/oW0C2DfhEQazYFApQKnqy3xFYSSm TapfjUykPtFjvLmbB2EMUaUCTPQUXU3J6ajTGADecKAOjME8/9a2jPVo+iZJhSAuYTn2tFyUL 2gp0DaaZC7S/UxCTqsNfjizXuha3aOJLgkmHpaKwO3Co/hMph1/H7LBM9sQK5nGzSL+gnt/rY sLwxAKa1C2lpteUSn8JyVBCSTxrpK4kXIk1wQ6fmwlqSQOYxU4XwIm8jLXkVBgWoFuutzAnOK bNGME9SxdHGFBDpRIWaHj+BSNJJOfkgf+0eQ5i21yWsGFuaMxqlzqYS2DCL2zyrIhzH+0H+I/ rXdlrtWU6n5uit9WV34TvUpDxa+sLKK4WdCLwUsAmHgpjQAhyAFMk+yOY2fEM/H2QwwoeMNfP lbszT88bsluOycA44sGr85myUx7SHkPG5EmzySVQiEMtxg9US5RQ2zxivyOA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/9E4w0ofAUHlUyBL02SpO80KyUGQ>
Subject: [Tools-discuss] missing line ends in generated TXT (from datatracker)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2019 06:18:37 -0000

On 21.10.2019 18:46, Julian Reschke wrote:
> On 21.10.2019 18:14, Dave Rice wrote:
>> Hi all,
>>
>>> On Oct 9, 2019, at 1:38 PM, Henrik Levkowetz <henrik@levkowetz.com
>>> <mailto:henrik@levkowetz.com>> wrote:
>>>
>>> Hi David,
>>>
>>> On 2019-10-09 17:32, Dave Rice wrote:
>>>> Thanks Henrik,
>>>>
>>>>> On Sep 20, 2019, at 5:26 PM, Henrik Levkowetz <henrik@levkowetz.com
>>>>> <mailto:henrik@levkowetz.com>> wrote:
>>>>>
>>>>> Hi Michael, David,
>>>>>
>>>>> On 2019-09-20 23:04, Michael Richardson wrote:
>>>>>>
>>>>>> Dave Rice <dave@dericed.com <mailto: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
>>>>>> <http://xml2rfc.ietf.org>;, which is a different installation,
>>>>>> supported by a different entity?
>>>>>
>>>>> Michael:  Umm, no, that redirects to tools.ietf.org
>>>>> <http://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.
>>>
>>> That sounds like a bug.
>>>
>>>> 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 atools.ietf.org <http://tools.ietf.org/>login, you
>>>>> can use the xml2rfc
>>>>> issue
>>>>> tracker athttps://trac.tools.ietf.org/tools/xml2rfc/trac/newticket,
>>>>> for
>>>>> xml2rfc issues, andhttps://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.
>>>
>>> Please don't put time into this; I'm perfectly happy to work from the
>>> xml
>>> file you found problematic on submission.  Just let me know the name
>>> of the
>>> draft in question, so I can pull it.
>>
>> I just uploaded this new version of the EBML specification to the
>> datatracker.
>>
>>
>> On lines 559-609 and 824-939 there are <sourcecode> nodes that contain
>> multi-line xml expressions. During the upload the idnit test showed no
>> issues or nits at all.  However in the resulting files at
>> https://datatracker.ietf.org/doc/draft-ietf-cellar-ebml/12/ the outputs
>> remove the line-breaks of the multi-line xml within the <sourcecode>
>> nodes. So in the HTML version the <sourcecode> is shown as a single
>> line, see
>> https://www.ietf.org/id/draft-ietf-cellar-ebml-12.html#name-ebml-schema-example,
>>
>> and in the plain text as well, see Section 11.1.1 of
>> https://www.ietf.org/id/draft-ietf-cellar-ebml-12.txt.
>>
>> In another document, I have been find/replacing the <sourcecode> node
>> with the older <artwork> node as a workaround.
>>
>> Best Regards,
>>
>> Dave Rice
>> ...
>
> I had the same problem and reported it as
> <https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/444>;.
>
> Best regards, Julian

Henrik,

could you please let us know what the status is? Does it make sense to
retry now?

Best regards, Julian