IETF Logo Mail Archive

Re: [rfc-i] Text in SVG diagrams

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 07 October 2021 13:00 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 99D6F3A1022; Thu, 7 Oct 2021 06:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=joelhalpern.com
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 Tt-e0bujA-x7; Thu, 7 Oct 2021 06:00:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CE0E3A00CF; Thu, 7 Oct 2021 06:00:31 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BBBA8E54C9; Thu, 7 Oct 2021 06:00:30 -0700 (PDT)
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 AEF9FE54C9 for <rfc-interest@rfc-editor.org>; Thu, 7 Oct 2021 06:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 we_kU1_bBW0w for <rfc-interest@rfc-editor.org>; Thu, 7 Oct 2021 06:00:26 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) by rfc-editor.org (Postfix) with ESMTPS id 24186E54BE for <rfc-interest@rfc-editor.org>; Thu, 7 Oct 2021 06:00:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4HQBJ96qQ8z6G9kn; Thu, 7 Oct 2021 06:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1633611625; bh=RZP+d/CMHpQ4ISdF/LSwAY+Y5hJfnd7vv77Vm+2O8FQ=; h=Date:Subject:To:References:From:In-Reply-To:From; b=fv7ya1KKhzyCWQdA+xsC/pUY9VKKgxcmbIM2njkZ3cx6NqaMlLzmEgcUtJoWSWEdo xOBfACh/trDX/YIwYveqRal45qwEMp5ZGlBWr5a4ZIeI7x6uFvCxV2FCxcWUWXCCSi rQgQ9Go3lED2wrGSzWRKL0Kwwr91AK3sA0rOZlVg=
X-Quarantine-ID: <r7e8uu8ZYWo2>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.22.111] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4HQBJ92DPHz6G8pk; Thu, 7 Oct 2021 06:00:24 -0700 (PDT)
Message-ID: <693f3307-5c53-94c9-dccb-b189094dd2fb@joelhalpern.com>
Date: Thu, 07 Oct 2021 09:00:22 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.1.2
Content-Language: en-US
To: Julian Reschke <julian.reschke@gmx.de>, rfc-interest@rfc-editor.org
References: <bbf9c212-818f-43bf-a1a1-ad606dcacd06@www.fastmail.com> <276e49d8-4c36-f6e7-2704-3f04514cd25f@gmail.com> <463ce937-0bc5-4e35-9329-0976c4a4950b@www.fastmail.com> <bace46f7-4d52-8544-a479-d31fa1c718be@it.aoyama.ac.jp> <883e2a04-82c3-f2f5-200a-86ff97f33aec@gmx.de>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <883e2a04-82c3-f2f5-200a-86ff97f33aec@gmx.de>
Subject: Re: [rfc-i] Text in SVG diagrams
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
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>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Given the range of ways things can be represented in SVG, and the 
demonstrated range of ways tools work, I would be amazed if a converter 
was simple.

Yours,
Joel

On 10/7/2021 3:22 AM, Julian Reschke wrote:
> Am 07.10.2021 um 08:37 schrieb Martin J. Dürst:
>> On 2021-10-07 12:48, Martin Thomson wrote:
>>> On Thu, Oct 7, 2021, at 14:37, Brian E Carpenter wrote:
>>>> It all depends on the drawing tool used.
>>>
>>> I'm aware of that.  I just think that if we use SVG we should take
>>> steps to avoid this sort of thing happening again.
>>
>> Very much so. Some drawing tools have a strong tendency to blow up
>> things. A simple rectangle can end up as something very complex.
>> Apparently, this also happens to text. I seem to remember there once was
>> a Website that lobbied against this, and for simpler SVG. Can't find it
>> anymore. But we should clearly try to avoid such stuff.
> 
> Absolutely.
> 
> In this case it seems the drawing tool tried to position each character
> separately.
> 
> Ideas:
> 
> - RFC Editor should do a sanity check on text handling
> - find out what produced these SVGs (otherwise beautiful!) and see
> whether it can be configured differently
> 
> ...and if that's not possible: write a simple post-processor that fixes
> the SVG (or embed that functionality into xml2rfc).
> 
> Best regards, Julian
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email