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

Carsten Bormann <cabo@tzi.org> Mon, 18 July 2022 22:42 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 7494AC13C527; Mon, 18 Jul 2022 15:42:34 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 Sej-0t494B0j; Mon, 18 Jul 2022 15:42:32 -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 BE975C13C501; Mon, 18 Jul 2022 15:42:29 -0700 (PDT)
Received: from smtpclient.apple (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 4Lmxmf2pz3zDCcB; Tue, 19 Jul 2022 00:42:26 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <1294992.1658179143@dooku>
Date: Tue, 19 Jul 2022 00:42:25 +0200
Cc: "Paul Duffy (paduffy)" <paduffy@cisco.com>, Kesara Rathnayake <kesara@staff.ietf.org>, Jay Daley <exec-director@ietf.org>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D980014C-790B-4243-BCFE-7D3537435FD3@tzi.org>
References: <MN2PR11MB3757223DDB24EC24024A0576B9A69@MN2PR11MB3757.namprd11.prod.outlook.com> <C74845D7-007B-43D9-89DC-8F1285890FA9@tzi.org> <1294992.1658179143@dooku>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/Pbupw8VK9eXjPM46Cy1dMAR0ChU>
Subject: Re: [Rfc-markdown] [rfc-i] CORRECTION RE: 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: Mon, 18 Jul 2022 22:42:34 -0000

On 18. Jul 2022, at 23:19, Michael Richardson <mcr@sandelman.ca> wrote:
> 
> 
> Carsten Bormann <cabo@tzi.org> wrote:
>> This:
> 
>>> <figure> <name>NMS View of Device State</name> <artset> <artwork
>>> type="svg"
>>> src="https://www.rfc-editor.org/materials/format/svg/stream.svg "/>
>>> <artwork type="ascii-art"> Artwork only available as SVG (PDF and
>>> HTML) </artwork> </artset> </figure>
> 
>> should work.  Any < or & you need in the “only available…” text need to
>> be escaped as &lt; and &amp;
> 
> Can this go into an example?

You mean as in documentation?

I was planning to wait for an xml2rfc with a fix for https://github.com/ietf-tools/xml2rfc/issues/767 to be released, which should be any day now.
That would make it easier to construct examples that do not rely on references to external files/URLs.

Grüße, Carsten