Re: [rfc-i] What do do about SVG

Carsten Bormann <cabo@tzi.org> Wed, 16 December 2020 22:49 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61D393A1276; Wed, 16 Dec 2020 14:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0UrrF197PcE; Wed, 16 Dec 2020 14:49:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 447733A1277; Wed, 16 Dec 2020 14:49:04 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9E90FF40764; Wed, 16 Dec 2020 14:48:56 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 925BBF40764 for <rfc-interest@rfc-editor.org>; Wed, 16 Dec 2020 14:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VGOxHkweWXAb for <rfc-interest@rfc-editor.org>; Wed, 16 Dec 2020 14:48:50 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id 8F45AF40763 for <rfc-interest@rfc-editor.org>; Wed, 16 Dec 2020 14:48:50 -0800 (PST)
Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Cx9KM3GpbzyTm; Wed, 16 Dec 2020 23:48:55 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <f564019-d8b1-76c2-2768-c135d834dc32@iecc.com>
Date: Wed, 16 Dec 2020 23:48:55 +0100
X-Mao-Original-Outgoing-Id: 629851735.024487-f4161b25f811711fa46bd3b50bdd056e
Message-Id: <4ACF279D-C830-4617-8B5B-BA699AC90821@tzi.org>
References: <f564019-d8b1-76c2-2768-c135d834dc32@iecc.com>
To: "John R. Levine" <johnl@iecc.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Subject: Re: [rfc-i] What do do about SVG
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 2020-12-15, at 20:47, John R. Levine <johnl@iecc.com> wrote:
> 
> Assuming that one of the goals is to have good tool support, what SVG tools do people use and what profiles do they support?

Assuming that we talk about authoring tools:

Inkscape and Omnigraffle were mentioned as the tools many people use for interactively creating graphics, maybe add Affinity Designer and Adobe Illustrator.  (All these also have some import function, although that is sometimes a bit of a hit or miss, as the internal data model may not be very congruent with all the complexities of SVG.)

There are also often import routes via EPS and PDF, pdf2svg/pdftocairo may be a general import mechanism for graphical information available in PDF form, which may in turn be generated by a zillion tools such as pandoc.

There are also tools that convert (potentially non-graphical) source-type information into graphics, which often support SVG output:

* goat and ditaa (for ASCII^Wtypewriter-art)
* mscgen (for message sequence charts)
* mermaid (for Flowchart, Sequence diagram, Class Diagram, State Diagram, Entity Relationship Diagram, User Journey, Gantt Chart, Pie Chart)
* plantuml (for UML diagrams, including much of the above)
* tex2svg (math formulae; can also use e.g. pandoc/pdftocairo)
* graphviz (general diagrams; DOT language, with neato, lefty)

Some of these tools assume they can use at least one gray scale level/color different from black/white; it is nearly impossible to compress this to bi-level (well, yeah, you can always use hatching or halftoning, for unwieldy and excruciatingly slow documents).

Graphs are also generated programmatically, e.g. using matplotlib or gnuplot.
Packages such as R have multiple SVG interfaces (e.g., svelte).

Note that not all of these have already been used for an RFC or I-D today, but this is like saying not all editors have been used for typing markdown — eventually, they will.  Use the right tool for the job.

Authors would probably do most of their rendering in browsers.

Grüße, Carsten

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest