hassanakbar4 / tractive-test

0 stars 0 forks source link

xml2rfc 2.10.0 (v3 xml): no section names generated #348

Closed hassanakbar4 closed 2 years ago

hassanakbar4 commented 6 years ago

component_Version_3_cli_txt resolution_invalid type_defect | by miek@miek.nl


xml2rfc version: 2.10.0

Using RFC 7991 to generate XML and let xml2rfc generate text, the following generates a section number by no title:

    <section>
      <name>Syntax</name>
      <t>The high-order bit of the IP fragment offset field is the only unused
bit in the IP header.  Accordingly, the selection of the bit position
is not left to IANA.</t>
      <t>The bit field is laid out as follows:</t>
    </section>

Attaching all XML and text output. There is also something weird the tag handling


Issue migrated from trac:348 at 2021-10-20 18:26:32 +0500

hassanakbar4 commented 6 years ago

@{"email"=>"miek@miek.nl", "name"=>nil, "username"=>nil} uploaded file rfc3514.xml (3.7 KiB)

XML used as input.

hassanakbar4 commented 6 years ago

@{"email"=>"miek@miek.nl", "name"=>nil, "username"=>nil} uploaded file rfc3514.txt (3.4 KiB)

text output from xml2rfc

hassanakbar4 commented 6 years ago

@{"email"=>"miek@miek.nl", "name"=>nil, "username"=>nil} uploaded file rfc3514.2.xml (2.4 KiB)

Correct XML

hassanakbar4 commented 6 years ago

@{"email"=>"miek@miek.nl", "name"=>nil, "username"=>nil} commented


With --v3 this fares better, leaves:

Parsing file x
x(3): Warning: The document date (2018-04-01) is more than 3 days away from today's date
x(2): Warning: Expected a category, one of std,historic,bcp,exp,info, but found none
x(43): Warning: No renderer for <bcp14> found
Created file x.txt
hassanakbar4 commented 5 years ago

@{"email"=>"henrik@levkowetz.com", "name"=>nil, "username"=>nil} changed status from new to closed

hassanakbar4 commented 5 years ago

@{"email"=>"henrik@levkowetz.com", "name"=>nil, "username"=>nil} changed resolution from ` toinvalid`

hassanakbar4 commented 5 years ago

@{"email"=>"henrik@levkowetz.com", "name"=>nil, "username"=>nil} commented


If you don't use --v3, none of the v3 xml elements will be recognized (because the renderer in use is the old pre-rfc7991 renderer). You should however se loads of validity warnings unless you turn those off with -n. Then you're on your own ,:-)