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

[Julian Reschke <[e-mail]>]

On 21.10.2019 18:14, Dave Rice wrote:
> Hi all,
>
>> On Oct 9, 2019, at 1:38 PM, Henrik Levkowetz <[e-mail]
>> <mailto:[e-mail]>> wrote:
>>
>> Hi David,
>>
>> On 2019-10-09 17:32, Dave Rice wrote:
>>> Thanks Henrik,
>>>
>>>> On Sep 20, 2019, at 5:26 PM, Henrik Levkowetz <[e-mail]
>>>> <mailto:[e-mail]>> wrote:
>>>>
>>>> Hi Michael, David,
>>>>
>>>> On 2019-09-20 23:04, Michael Richardson wrote:
>>>>>
>>>>> Dave Rice <[e-mail] <mailto:[e-mail]>> 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