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

[Dave Rice <[e-mail]>]

Thanks Henrik,

> On Sep 20, 2019, at 5:26 PM, Henrik Levkowetz <[e-mail]> wrote:
> 
> Hi Michael, David,
> 
> On 2019-09-20 23:04, Michael Richardson wrote:
>> 
>> Dave Rice <[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, 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