Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.25.0

[Henrik Levkowetz <[e-mail]>]

I see Robert's responses landed while I was typing my response ,:-)

On 2019-08-29 22:24, Henrik Levkowetz wrote:
> Hi Bob,
> 
> On 2019-08-29 21:22, Robert Moskowitz wrote:
>> 
>> 
>> On 8/26/19 8:44 AM, Henrik Levkowetz wrote:
>>> Hi,
>>>
>>> This is an automatic notification about a new xml2rfc release,
>>> v2.25.0, generated when running the mkrelease script.
>> 
>> Notes on my experience with the upgrade:
>> 
>> I get the standard warning:
>> 
>> DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 
>> 2020. Please upgrade your Python as Python 2.7 won't be maintained after 
>> that date. A future version of pip will drop support for Python 2.7.
>> 
>> I have both Python2 and 3 installed on my Fedora 30 system.
> 
> This warning indicates either that the default python is still 2.7, or
> that the pip command you are running is symlinked to pip-2.7.
> 
>> What is causing this message?  An old version of pip or xml2rfc?
> 
> Pip.  The pip that comes with Python 2.7 gives the warning above.
> 
> Irrespective of which pip and python you use (2.7, 3.5, 3.6, 3.7),
> the installed version of xml2rfc now supports vocabulary v3.
> 
>> Is there a way to install xml2rfc v3 to start checking it out without 
>> loosing v2?
> 
> xml2rfc v2 and v3 are supported by the same install.  In order to produce
> v3 output, use 'xml2rfc --v3 ...'.  In order to convert your v2 xml files
> to v3 xml, use 'xml2rfc --v2v3 ...'.
> 
> Note that when speaking about 'v3' xml2rfc, there is a certain need to
> indicate which aspect of xml2rfc v3 support you are referring to:
> 
> There is both the matter of the v3 xml vocabulary, where many v2 constructs
> are deprecated; and there are the v3 formatters, which are completely
> rewritten to handle the v3 xml.
> 
> Now, having made that clear, I'm afraid that the following may cause some
> blurring again, but it's been done in the interest of making forward progress
> easier:  If you invoke one of the v3 formatters, by saying for instance
> 'xml2rfc --v3 --text ...', but your input file uses deprecated v2 elements,
> those will be quietly converted internally, using the v2-to-v3 converter,
> and then handed to the v3 formatter.  This of course adds a bit of magic
> to the process, and you will have better control of your output if you work
> with clean v3 input files.  Converting your v2 files to v3 with --v2v3 should
> give you a good starting point for that.
> 
> I hope that helps.
> 
> 
> Best regards,
> 
> 	Henrik
> 
> 
> 
> _______________________________________________
> xml2rfc mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/xml2rfc
>