Re: [xml2rfc] Official tool for extracting sourcecode
Carsten Bormann <cabo@tzi.org> Thu, 27 July 2023 14:26 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E49BC14CE5D for <xml2rfc@ietfa.amsl.com>; Thu, 27 Jul 2023 07:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VN7SnGHk0Iyp for <xml2rfc@ietfa.amsl.com>; Thu, 27 Jul 2023 07:26:09 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 389BDC14F748 for <xml2rfc@ietf.org>; Thu, 27 Jul 2023 07:26:08 -0700 (PDT)
Received: from smtpclient.apple (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RBY3K586TzDCg5; Thu, 27 Jul 2023 16:26:05 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <75b922df-2aaa-d2d8-1a36-7f7a72379428@htt-consult.com>
Date: Thu, 27 Jul 2023 16:25:55 +0200
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <75AB091D-E809-4FC8-A21F-8FCC198839FB@tzi.org>
References: <75b922df-2aaa-d2d8-1a36-7f7a72379428@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/1DfqrRG9dIh__EL-Ujf3RgvroYI>
Subject: Re: [xml2rfc] Official tool for extracting sourcecode
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2023 14:26:15 -0000
On 27. Jul 2023, at 16:21, Robert Moskowitz <rgm@htt-consult.com> wrote: > > Perhaps datatracker needs a better tool and Carsten's is were to start? Am I that "out there" in using sourcecode blocks and then wanting doc readers to be able to use the source code? It sure works for me. I do want to fix the way the filenames are derived (too much scaredy-cat programming at the moment), and then we can go and check this on a wider scale. (I would expect the source-code blocks of all 8650+ RFCs to be on the web ready for consumption, as well as on rsync. For I-Ds, I would people to go with the tool.) Grüße, Carsten
- [xml2rfc] Official tool for extracting sourcecode Robert Moskowitz
- Re: [xml2rfc] Official tool for extracting source… Carsten Bormann