IETF Logo Mail Archive

Re: [Tools-discuss] XML/TXT to kramdown

Carsten Bormann <cabo@tzi.org> Fri, 05 April 2024 05:05 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD1EC151061 for <tools-discuss@ietfa.amsl.com>; Thu, 4 Apr 2024 22:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.188
X-Spam-Level:
X-Spam-Status: No, score=-4.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=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 Vat-PteJD5Xk for <tools-discuss@ietfa.amsl.com>; Thu, 4 Apr 2024 22:05:21 -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 25381C14CE53 for <tools-discuss@ietf.org>; Thu, 4 Apr 2024 22:05:18 -0700 (PDT)
Received: from smtpclient.apple (p5089a101.dip0.t-ipconnect.de [80.137.161.1]) (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 4V9mdR3jv2zDCcW; Fri, 5 Apr 2024 07:05:15 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5B5797E8-A894-4104-8D22-A541A7A78CDE@eggert.org>
Date: Fri, 05 Apr 2024 07:05:04 +0200
Cc: tools-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <39FA57B7-CDE3-497F-9D90-47C9212C4712@tzi.org>
References: <be232336-a5e4-4886-8d4e-aad82c68e442@stpeter.im> <6B39A510-B601-4564-BEE6-92E22505B877@tzi.org> <D18911AA-6127-45AB-9CB0-E509227B5B35@eggert.org> <015BCA2E-193F-49A9-95CC-65965371370C@tzi.org> <5B5797E8-A894-4104-8D22-A541A7A78CDE@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/89ODO4RglCrf3zsCOYgIFGuhifA>
Subject: Re: [Tools-discuss] XML/TXT to kramdown
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2024 05:05:27 -0000

On 5. Apr 2024, at 06:59, Lars Eggert <lars@eggert.org> wrote:
> 
> Hi,
> 
> On Apr 5, 2024, at 00:57, Carsten Bormann <cabo@tzi.org> wrote:
>> Yes.  It would also create the illusion that you can freely oscillate between using XML and kramdown-rfc as your source form.  That will never work.  (Up-conversion is hard.)
> 
> I don't think that's a given.

Well, I *have* seen people trying to do that, so it is not a theoretical concern.

> At least whatever README you provide can make it very clear that's not considered a supported use case.

As if people were reading (and heeding!) READMEs :-)

(The main reason I haven’t open-sourced the code is that its design is all wrong, conflating conversion to the markdown information model with generating markdown syntax, and I need to do a round of serious refactoring to fix that and the ensuing bugs before people start adding to it.  But the rather obvious unintended consequence I alluded to above does keep me awake at night.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email