[Tools-discuss] xml2rfc in --v2 mode -- bug report?

[John C Klensin <[e-mail]>]

Hi.   I have an old document, in xml2rfc v2 format, whose
content I'm trying to upgrade.  When I run
   xml2rfc DocName.xml --v2
(with version 3.12.7) I get a series of messages that look like

 Warning:
	file:/C:/Users/Klensin/AppData/Local/Programs/Python/Pyt
	hon37/lib/site-packages/xml2rfc/templates/rfc2629-xhtml.
	ent is no longer needed as the special processing of
	non-ASCII characters has been superseded by direct
	support for non-ASCII characters in RFCXML.

The source does not contain any references to rfc2629-xhtml.ent.
It does, of course, contain 
	<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
as well as the DOCTYPE statement that specifies the DTD

Are these warnings actually addressed to something in the DTD or
stylesheet file than should be cleaned out and, if so, how does
that get done?

Also, I see an additional statement that says 

	Warning: The 'docName' attribute of the <rfc/> element
	should have a revision number as the last component:
	docName="draft-foo-bar-02".

Not a huge problem as long as it is just a warning, but I'm
almost certainly not the only one who uses odd names to keep
track of evolving working versions of a draft between versions
that actually get posted.  I typically use draft-docname-NNa,
draft-docname-NNb, etc.  I've seen signs of others using
draft-docname-NN-DATE or other conventions).  I don't know how
best to do this (other than leaving the issue to the submission
tool), but, if the intent is that people read, study, and act on
warnings, keeping down the noise would be helpful.

thanks,
   john

p.s. Before someone asks why I don't just convert to v3 and be
done with it, when I try that, the conversion appears to work
(no error messages, no warning messages other than the one above
about /rfc2629-other.ent, file created successfully).  However,
when I try to process that file, I get an impressive traceback
whose entries appear to be pointing into different Python
modules followed by "KeyError: 'day'".   If anyone feels like
having a look at that, let me know offlist.  Otherwise, I need
to stay with v2 until I have much more time on my hands.