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

Alice Russo <arusso@amsl.com> Mon, 18 July 2022 20:38 UTC

Return-Path: <arusso@amsl.com>
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 84631C13C535; Mon, 18 Jul 2022 13:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=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 nHHo9gq-Lex4; Mon, 18 Jul 2022 13:38:25 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 DEAB5C13C532; Mon, 18 Jul 2022 13:38:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id CD450424B455; Mon, 18 Jul 2022 13:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTfsUPEX80jG; Mon, 18 Jul 2022 13:38:24 -0700 (PDT)
Received: from [192.168.4.33] (c-24-17-19-210.hsd1.wa.comcast.net [24.17.19.210]) by c8a.amsl.com (Postfix) with ESMTPSA id 8CB3C424B44D; Mon, 18 Jul 2022 13:38:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <C74845D7-007B-43D9-89DC-8F1285890FA9@tzi.org>
Date: Mon, 18 Jul 2022 13:38:24 -0700
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: <921C63EA-E7CA-490C-8EA0-73C5535CB4CA@amsl.com>
References: <MN2PR11MB3757223DDB24EC24024A0576B9A69@MN2PR11MB3757.namprd11.prod.outlook.com> <C74845D7-007B-43D9-89DC-8F1285890FA9@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/VGO_xEEHIsLNB-g0EWQNUqQ9vk4>
Subject: Re: [Rfc-markdown] CORRECTION RE: [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: Mon, 18 Jul 2022 20:38:29 -0000

Side note: If the input file provides artwork type="svg" (without a corresponding artwork type="ascii-art"), then xml2rfc automatically puts a message in the text output. (There's a related issue: https://github.com/ietf-tools/xml2rfc/issues/617.)

Alice

> On Jul 18, 2022, at 12:41 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> Hi Paul,
> 
> 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;
> 
> Grüße, Carsten
> 
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown