IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Sun, 24 October 2021 20:40 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E5B63A085A; Sun, 24 Oct 2021 13:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v08mUnv1_4C9; Sun, 24 Oct 2021 13:40:17 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 348BD3A0825; Sun, 24 Oct 2021 13:40:17 -0700 (PDT)
Received: from [192.168.217.118] (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Hcqhk4X7hz30Sr; Sun, 24 Oct 2021 22:40:06 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CADyWQ+G0kbe27wN=p4Zjx4VJFZS7889ytfkos+DjZ19AbccbDg@mail.gmail.com>
Date: Sun, 24 Oct 2021 22:40:06 +0200
Cc: Robert Moskowitz <rgm@htt-consult.com>, rfc-markdown@ietf.org, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 656800805.974104-3cfce6ec26649f6890f17233c004df3e
Content-Transfer-Encoding: quoted-printable
Message-Id: <4FF224D5-90E4-45C4-83C9-C4DC4614FD66@tzi.org>
References: <ab61777c-5446-c7c8-1ba1-ec8d8bde2cd4@htt-consult.com> <2A985F36-1332-497F-8DDC-2531245FA8A3@tzi.org> <CADyWQ+FQLoK047A=34VdayGu0s4Q9pnL0FnXkcFs=uAbpcH-Zg@mail.gmail.com> <17adc707-6d65-3455-7fb0-ae82d88e0b77@htt-consult.com> <CADyWQ+G0kbe27wN=p4Zjx4VJFZS7889ytfkos+DjZ19AbccbDg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/X45VfE71JRdJmfDzDWBxI1Qu0_E>
Subject: Re: [Rfc-markdown] [xml2rfc] Is the --v3 switch still needed?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2021 20:40:21 -0000

On 2021-10-24, at 22:35, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
> I am on ver 3.10.0, but like how do you know that the proper txt was built and not some fall back to whatever v2 would do?

The v3 formatter uses a different date format; that is usually the easiest giveaway.

Compare https://datatracker.ietf.org/doc/draft-ietf-emailcore-rfc5322bis/
29 September 2021 (v3 formatter date format)

with https://datatracker.ietf.org/doc/draft-ietf-emailcore-rfc5321bis/
October 24, 2021 (v2 formatter date format)

Grüße, Carsten

v2.8.7 | Report a Bug | By Email