Re: [xml2rfc] Current xml2rfc produces errors on published RFCs

This seems to be introduced with 
https://trac.ietf.org/trac/xml2rfc/ticket/581 by restricting section IDs 
to be in `appendix-A.1` format without a backward compatibility.

  --Kesara

On 2/08/21 5:10 pm, Brian E Carpenter wrote:
>  From a brief experiment, the xml2rfc convertor at https://xml2rfc.tools.ietf.org/experimental.html simply can't deal with the xml files at https://www.rfc-editor.org/info/rfcXXXX, right back to RFC8650.
> 
> The specific element causing the problem appears to be pn="xxx" which is like anchor only different. The published XML is littered with pn's.
> 
> Regards
>     Brian
> 
> On 02-Aug-21 16:10, Martin J. Dürst wrote:
>> On 2021-08-02 10:49, John R Levine wrote:
>>> When I run rfc8799.xml or rfc9001.xml through the current version of
>>> xmlrfc, it says:
>>>
>>> Error: Found no element to match the <xref> target attribute 'section-a.1'
>>>
>>> When I look at the XML, the target is there and this presumably worked
> 
>>> when the RFCs were published.
>>
>> I think it would be a good idea to add the above two documents to a test
>> suite to avoid regressions. And use some kind of continuous integration
> 
>> testing (if that's already done, that's great).
>>
>> Regards,   Martin.
>>
>>> Regards,
>>> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>>> Please consider the environment before reading this e-mail. https://jl.ly
>>>
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
> 

-- 
Kesara Rathnayake
Senior Software Development Engineer - IETF LLC
krathnayake@ietf.org