Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.25.0
Carsten Bormann <cabo@tzi.org> Fri, 30 August 2019 04:46 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 5464D120C9B; Thu, 29 Aug 2019 21:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 WVr-vsT6kIDy; Thu, 29 Aug 2019 21:46:03 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA3EB120C9A; Thu, 29 Aug 2019 21:46:02 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46KRkd3kjJzyVb; Fri, 30 Aug 2019 06:46:01 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com>
Date: Fri, 30 Aug 2019 06:46:01 +0200
Cc: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 588833159.522516-bedb8df44ee44b0403857f2bb4e6c74a
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2F74A60-1620-4978-8C78-D74AC80B53B0@tzi.org>
References: <E1i2EMD-0002SA-UW@durif.tools.ietf.org> <d82ab9f2-5913-ad0e-dc05-2be319480a3c@htt-consult.com> <e206317e-bb51-c9e6-9dc2-c9d86b13b9da@levkowetz.com> <8fdc91d2-a683-eb4d-04f1-ade8e424436f@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/JNXxTOdn99jGphieQdCzr1QeoM8>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.25.0
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: Fri, 30 Aug 2019 04:46:04 -0000
On Aug 29, 2019, at 22:49, Robert Moskowitz <rgm@htt-consult.com> wrote: > > I also foresee a possible challenge in that I do a lot of copy and paste from old drafts to new, and I could end up dragging something into converted draft that is not for v3 from an unconverted old file. For the next decade or so, the v2v3 avenue is going to be the one that many drafts will use. Going for v3 only source gives you more control (maybe; some of this control is wrested away from you in the preptool), but has little practical value to most RFC authors in an organization where documents take 3 to 7 years to gestate. Grüße, Carsten
- [Rfc-markdown] New xml2rfc release: v2.25.0 Henrik Levkowetz
- [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2… Julian Reschke
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Miek Gieben
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Henrik Levkowetz
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc] bcp14, was: [xml2rfc… Fred Baker
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Dave Lawrence
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Henrik Levkowetz
- Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Julian Reschke
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Sparks
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Sparks
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Henrik Levkowetz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Henrik Levkowetz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc] New xml2rfc release:… Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Carsten Bormann
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Carsten Bormann
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Carsten Bormann
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Robert Moskowitz
- Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xm… Julian Reschke
- Re: [Rfc-markdown] [xml2rfc-dev] bcp14, was: New … Julian Reschke