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

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 25 November 2023 09:14 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 51659C15C282 for <rfc-interest@ietfa.amsl.com>; Sat, 25 Nov 2023 01:14:55 -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 6XBanlB-nchO for <rfc-interest@ietfa.amsl.com>; Sat, 25 Nov 2023 01:14:51 -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)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48BDEC153CA8 for <rfc-interest@rfc-editor.org>; Sat, 25 Nov 2023 01:14:51 -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 46B2F1F427; Sat, 25 Nov 2023 09:14:49 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="kfcI279i"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 4C25BA0E98; Sat, 25 Nov 2023 10:14:32 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1700903672; bh=q9+BZRmYpgoDf8pYdwiurMxCOPpoEK0V1UzfEelTWio=; h=From:To:Subject:In-reply-to:References:Date:From; b=kfcI279iM/WQgM9xJlYyk96H36uxBLu9eDKDaRcAVZniqNoWhHQ3npYUkAQDwj2vG d1IODQjvpFSAhAPU6qHaLR/+IcAlBnun14S5dtaJvVbKzC/gEYD7iNtkeP/N6d3nPT cDo2QjEByYzkJmV96RiNq6aP4tlMFaXOdsKnmp7DTVc3GJlUZdlzsdBt0P3NDPaf1U f5YccU054ErUjFvxBdI1MiJUs6SdNTHL2g2S83PzSWnZXCNt8vOEVLjsqGhh0dDiYr BWEDfHfOtVISmCN2bQjqVpViIddqAAMEJPpA2acipdLws2jVzPTlIx+WZ3OGDUQ+DU MiBelEr/cTkBQ==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 49700A05F3; Sat, 25 Nov 2023 10:14:32 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>, rfc-interest@rfc-editor.org
In-reply-to: <B67B9F9D-6B0F-4B35-A92E-95982BC1EB10@tzi.org>
References: <310371.1700735021@dyas> <6062AA58-6798-4B82-9FE3-6FA1AF05F7CD@vpnc.org> <B67B9F9D-6B0F-4B35-A92E-95982BC1EB10@tzi.org>
Comments: In-reply-to Carsten Bormann <cabo@tzi.org> message dated "Thu, 23 Nov 2023 16:27:35 +0100."
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:14:32 +0100
Message-ID: <390399.1700903672@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/ZBAgyrDmfk6pVeu87yw_sZuM9iQ>
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:14:55 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > I don’t understand why we would want the HTML file to autonomously
    > provide extraction of attachments; I’m more interested in having a
    > separate URI for each attachment similar to the way Paul Kyzivat
    > showed.

For many people, including much of the IETF author space, that's where they see the image.

If extracting the image isn't slightly discoverable via that path, then the
route they are going to take is the PrtSc key, which leads to sad raster
diagrams.  (It also makes it harder to track where the image has been used,
but that's a different problem)

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