On 10/9/19 2:52 AM, Martin J. Dürst wrote:
On 2019/10/09 09:00, Job Snijders wrote:
Between the name of the tool (note the 2 in "xlm2rfc"), the industry's
transition from python 2 to python 3, and IETF's transition from the
v2 to the v3 RFC XML format, it is no surprise to me end users easily
become confused. A simple strong message that python2 can't be used
might be helpful, even if it appears somewhat unforgiving.
What about changing xml2rfc's name to xml3rfc? That way, xml3rfc, python
3, v3 of RFC XML, and pip3 would all align :-).
because it is suppose to be translated as "xml formatting TO RFC
formatting"?
And there is some confusion? It was xml2rfc back in v1.
Finally who remembers that originally it was called Blutooth after King
Harald Blutooth? (or somesuch spelling), and despite considerable
documentation as to the origin of the name, the press won and it became
Bluetooth?
:)
