IETF Logo Mail Archive

Re: [Rfc-markdown] [rfc-i] Problem with Kramdown tooling and figures?

Carsten Bormann <cabo@tzi.org> Wed, 08 June 2022 15:12 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 87BB2C14CF13; Wed, 8 Jun 2022 08:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 s5oPWTd933na; Wed, 8 Jun 2022 08:12:18 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (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 7BF59C14F613; Wed, 8 Jun 2022 08:12:17 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (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 4LJ9gg3B0NzDCbt; Wed, 8 Jun 2022 17:12:15 +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: <MN2PR11MB375760E12BFCDEB0ABA516BAB9A49@MN2PR11MB3757.namprd11.prod.outlook.com>
Date: Wed, 08 Jun 2022 17:12:15 +0200
Cc: Jay Daley <exec-director@ietf.org>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 676393935.0736769-a96a5edf9da08c0d2416fb95c10f1f8b
Content-Transfer-Encoding: quoted-printable
Message-Id: <28E28C6A-5C59-41AB-BB2C-A500CB48B89E@tzi.org>
References: <MN2PR11MB37570F4603464349B5DFFE5AB9A59@MN2PR11MB3757.namprd11.prod.outlook.com> <5E5D4003-E3D8-49B2-B14D-5D4AC7ADA0A3@tzi.org> <MN2PR11MB3757F2B3467FA1B188A1294DB9A49@MN2PR11MB3757.namprd11.prod.outlook.com> <7FFFF173-7D5F-4000-BDD1-9B407767C48E@ietf.org> <MN2PR11MB375776E0FFAA1023CFE4334AB9A49@MN2PR11MB3757.namprd11.prod.outlook.com> <99D6215E-50DA-422C-96D1-50949951394D@ietf.org> <MN2PR11MB3757A781285E16B585A6F841B9A49@MN2PR11MB3757.namprd11.prod.outlook.com> <MN2PR11MB375760E12BFCDEB0ABA516BAB9A49@MN2PR11MB3757.namprd11.prod.outlook.com>
To: "Paul Duffy (paduffy)" <paduffy=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/RNf8ST68T7myVVSVO3n_S7d-pho>
Subject: Re: [Rfc-markdown] [rfc-i] Problem with Kramdown tooling and figures?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 08 Jun 2022 15:12:21 -0000

On 2022-06-08, at 17:06, Paul Duffy (paduffy) <paduffy=40cisco.com@dmarc.ietf.org> wrote:
> 
> ... results in the following XML …

This is the one I fixed in kramdown-rfc 1.6.11, just pushed.
(I’m not sure how quickly that is going up on author-tools.)

Grüße, Carsten

Oh, and:

> FYI a quick kramdown test using a correct example from the templates…

The example is not “correct” as far as current xml2rfc usage goes: it does not have an ascii-art branch in the artset.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email