Re: [rfc-i] getting SVG of RFC diagrams

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 25 November 2023 09:11 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F21C153CA8 for <rfc-interest@ietfa.amsl.com>; Sat, 25 Nov 2023 01:11:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 SE34ylRBHT_I for <rfc-interest@ietfa.amsl.com>; Sat, 25 Nov 2023 01:11:45 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 CBEC7C152574 for <rfc-interest@rfc-editor.org>; Sat, 25 Nov 2023 01:11:44 -0800 (PST)
Received: from dyas.sandelman.ca (dynamic-002-247-250-179.2.247.pool.telefonica.de [2.247.250.179]) by relay.sandelman.ca (Postfix) with ESMTPS id D26471F427; Sat, 25 Nov 2023 09:11:42 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="lcXrXJBF"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 6A7BFA0E98; Sat, 25 Nov 2023 10:11:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1700903481; bh=jY+4cJcKtnwkf9uDiSupK600Cl1Ud0oANznAZQBKuU0=; h=From:To:Subject:In-reply-to:References:Date:From; b=lcXrXJBFSh4yRHmAl4YkL7kajlT9RkKT319L1fUxg+EILlr914zGc5z5lPS5HcZOg DP6+mdRRlZctXKd/i6ZNrGiO5X5Ki0i2QnFIlS91k1HYpeiYQm0ZkK9fQ0LlZTb9D9 mC7OHS7o72z8Xc5nqjyJlh3Yt2EgvSg2aERNKCzG/8nU1nhp2zBmw4qMf2DYdYF6Mw aNQ9KncA3iVDeH1u1uQwaegcW5iqPLNrOWSIXAryrZLYG70RepuB8eDtkTaAP3K1CZ PgVva7kFDTYjGNfbnM2D+0nVX5maff1uQfWu1rbHnCJt+o9c8AW4TzxCRQQBU1yjd3 kD1b56CbN9rEg==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 67FC7A05F3; Sat, 25 Nov 2023 10:11:21 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Paul Hoffman <paul.hoffman@vpnc.org>, rfc-interest@rfc-editor.org
In-reply-to: <6062AA58-6798-4B82-9FE3-6FA1AF05F7CD@vpnc.org>
References: <310371.1700735021@dyas> <6062AA58-6798-4B82-9FE3-6FA1AF05F7CD@vpnc.org>
Comments: In-reply-to Paul Hoffman <paul.hoffman@vpnc.org> message dated "Thu, 23 Nov 2023 07:16:43 -0800."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 25 Nov 2023 10:11:21 +0100
Message-ID: <390321.1700903481@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/hPn7MFsEM8k7r-9tM5UZ_NnAseU>
Subject: Re: [rfc-i] getting SVG of RFC diagrams
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Nov 2023 09:11:50 -0000

Paul Hoffman <paul.hoffman@vpnc.org> wrote:
    >> The question is: how to make these SVG files more easily available
    >> from the HTML version of the RFC?

    > Pedantically, it is not an SVG file but instead is an SVG element of
    > the HTML. The first figure in that RFC has the code: <div
    > class="alignCenter art-svg artwork" id="section-3-2.1.1"> <svg
    > xmlns="http://www.w3.org/2000/svg" version="1.1" height="416"
    > width="560" viewBox="0 0 560 416" class="diagram" text-anchor="middle"
    > font-family="monospace" font-size="13px">

    > A possible (and backwards-compatible!) solution would be to add an id
    > to each SVG element, which would then be a hoverable link. I don't know
    > if this in fact works; HTML experts here would. If it could work,
    > please propose it for XMLRFCv3.1 over on the RSWG.

Through the magic of human editable formats, I guess that I can try this:

<figure id="figure-1">
        <div id="section-3-2.1">
          <div class="alignCenter art-svg artwork" id="section-3-2.1.1">
<svg id="figure-01" xmlns="http://www.w3.org/2000/svg" version="1.1" height="416" width="560" viewBox="0 0 560 416" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px">

I added id="figure-01"

but that didn't do anything for me. At least via file://
Maybe I mis-understood.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*