Re: [Rfc-markdown] [xml2rfc] Is the --v3 switch still needed?

In version 3.10.0 It appears the default for --v3 is True, which is what I
would have done:

    formatoptions.add_argument('--v3', action='store_true', default=True,
                           help='with --text and --html: use the v3
formatter, rather than the legacy one')

Try it w/out the --v3 if you are up to date (and if not....)

tim

On Sun, Oct 24, 2021 at 12:33 PM Carsten Bormann <cabo@tzi.org> wrote:

> On 2021-10-24, at 17:07, Robert Moskowitz <rgm@htt-consult.com> wrote:
> >
> > Do we still need to include the --v3 switch on the command line?
> >
> > particularly if we have
> >
> > <rfc ... version="3">
> >
> > getting tired typing it in all the time...
>
> It is generally a big thing to change a command line interface, as the
> command may be embedded in a lot of scripts (it certainly is for xml2rfc),
> which then do unexpected things.
>
> I happen to be thinking about a related kind of change for kdrfc, the
> “driver” command for kramdown-rfc2629.  That change would require some
> indication of v3ness in the markdown file; but maybe that same indication
> would be a nice way to get rid of needing to override old defaults (such as
> setting stand_alone: true, consensus: true if category: std; also the need
> to declare ipr: trust200902 or pi: [toc, sortrefs, symrefs, comments],
> etc.).
>
> Feedback about the latter welcome to rfc-markdown@ietf.org.
>
> Grüße, Carsten
>
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown
>