IETF Logo Mail Archive

Re: [rfc-i] No, constraining to a custom SVG profile is not trivial

Leonard Rosenthol <lrosenth@adobe.com> Thu, 16 January 2020 14:37 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 9B2E8120043 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 16 Jan 2020 06:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.751
X-Spam-Level:
X-Spam-Status: No, score=-4.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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=adobe.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 1h2Cqq4lgc6f for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 16 Jan 2020 06:37:01 -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 065A512008C for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 16 Jan 2020 06:37:01 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DAEA6F406F2; Thu, 16 Jan 2020 06:36: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 54CD3F406F2 for <rfc-interest@rfc-editor.org>; Thu, 16 Jan 2020 06:36:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=adobe.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 E8T1WDIxkVS4 for <rfc-interest@rfc-editor.org>; Thu, 16 Jan 2020 06:36:52 -0800 (PST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2084.outbound.protection.outlook.com [40.107.220.84]) by rfc-editor.org (Postfix) with ESMTPS id 43D3CF406F0 for <rfc-interest@rfc-editor.org>; Thu, 16 Jan 2020 06:36:51 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PjTm475hnNwhG7zTzDKpcpKKDJagLVi4yhT5PeuYbPhdoXPzFOZCdO+aiY0wSRDnB1q2iygrgnDAFeF25YUOzdSh7TWRkqn+vQLUhlRzoGmtGFjeJqhO3QQTaHzi7lVFYsHuvA5dBDjeO0qa0KmPJwkjCJtIYWWFV46h1xTOZXGNGrd2hD/9lo8MQiAdZhAm9Q74H9KhSPpO2/k4w4u6rOhvT2YxoDNTIg1baYAU76iQ5NQ/HZjkL+gxpELYHZEPbpYFiHc9kSaK/Qj90KSPvmYKBc7N8s3UgaIYch9a97PDGPpyecCf7JUhGpjlgcY0RIQ++YTwKpN2+9bpeOqXTA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Rlk3yYNw7bSwwttTZ4lqTKelKFMmUX97eC7JZN1Wdos=; b=N8Q0ZicrinTy/VcdHmosffFT4307etQCw+ABdxoDf/lbQ5xMsNbhGNFaFcKyX2Cj0n9xg0/l3leodRA1KwpHTAR0223GMWlbC8VG/ivYmA2dn2YxTTjIu3mcLFqZYQ3EFJ1xnX/hJ23l9l1NOUwEPcijvGACHg4nRoqzrLDNwx39TDuS9ui5f3PLT+84xma36NO9lTaqJONDyfy51JmSqZfds0yZ9I4SqHlGWcR0J16hQTtnxi7j49gqJuxEPfDPLz48qq8j+xhoP08uoJ2WagOwqdZe8Z2e35Exn4UrbsOGuWYLHQR40frTAeKvNqDY1cW4kRvx/nuoz7hAjum4Og==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=adobe.com; dmarc=pass action=none header.from=adobe.com; dkim=pass header.d=adobe.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adobe.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Rlk3yYNw7bSwwttTZ4lqTKelKFMmUX97eC7JZN1Wdos=; b=m9n1cX+y1stpcRAQziBTkmQXycWrLKWJpDZlpJDXwE/1WpBxJ91w77PvCA/Vn1zMrSmCJFEcE8afrEkDEy4UkYXR10B8HZsvuOlEfYOJfS8+NVafNTdh3WE3RNMlFOmH+vMj1Zd0vqPr1Uig+onWSVgjzlMcczKuUj5AfN7cqyw=
Received: from MN2PR02MB6992.namprd02.prod.outlook.com (20.179.223.74) by MN2PR02MB6656.namprd02.prod.outlook.com (52.135.50.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.20; Thu, 16 Jan 2020 14:36:50 +0000
Received: from MN2PR02MB6992.namprd02.prod.outlook.com ([fe80::bc90:8089:6718:861b]) by MN2PR02MB6992.namprd02.prod.outlook.com ([fe80::bc90:8089:6718:861b%5]) with mapi id 15.20.2623.015; Thu, 16 Jan 2020 14:36:50 +0000
From: Leonard Rosenthol <lrosenth@adobe.com>
To: Doug Royer <douglasroyer@gmail.com>, RFC Interest <rfc-interest@rfc-editor.org>
Thread-Topic: [rfc-i] No, constraining to a custom SVG profile is not trivial
Thread-Index: AQHVy+B+fK9mbLxji0OmSjNG5L+GI6fsd7CAgAAYjICAABACAIAAFCiAgABUzIA=
Date: Thu, 16 Jan 2020 14:36:50 +0000
Message-ID: <3EA5DBDE-A936-4AD9-A5F4-83CC043AE027@adobe.com>
References: <CAMm+LwiXhhJO7qYi41+DC4W7uMUVipXqyq75Fq2vagA1ppJNdA@mail.gmail.com> <10cca93f-a8b8-4c42-0653-3b12fa67ad12@gmail.com> <CAMm+LwgA-1UffBfrH-Y3J6pfh7ni9kNrndp=gHNyUyi5j=oLxg@mail.gmail.com> <53607da4-6608-783b-b875-65551e3add19@gmail.com> <c25db7f1-509d-062d-c5bf-ffa48bd892fb@gmail.com>
In-Reply-To: <c25db7f1-509d-062d-c5bf-ffa48bd892fb@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lrosenth@adobe.com;
x-originating-ip: [192.147.118.254]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 90366eac-fd7a-4124-8071-08d79a9185fc
x-ms-traffictypediagnostic: MN2PR02MB6656:
x-microsoft-antispam-prvs: <MN2PR02MB6656C5A3B6072394E6414340CD360@MN2PR02MB6656.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 02843AA9E0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(39860400002)(396003)(136003)(376002)(189003)(199004)(966005)(2906002)(5660300002)(45080400002)(6506007)(36756003)(786003)(81166006)(53546011)(6512007)(81156014)(8936002)(8676002)(26005)(66446008)(76116006)(64756008)(66556008)(66476007)(66946007)(2616005)(110136005)(186003)(86362001)(316002)(478600001)(33656002)(71200400001)(6486002)(91956017); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR02MB6656; H:MN2PR02MB6992.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: adobe.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vlnECuSyziHl9PeLPFDVFY/FWwx50i1TiUzAg29Jtl2CCGiy4EvS4wPho0osY4y4Zo/kloXio/r3Bz3Woo2Tjou8wI5nnYps7SOspwdoQUMFhlX+36w0ytLNlvVFfvpiCz5N89xNrKb6RUHxyymBgSZFVC2Qo3OLI3OOyBS5I6lqwEodyMuOkLv4YTqTL033S5y30DSsUI12iS/uvfb0QO80v3JV75mS06p+U6Pf3EOHmhKuEqEMjylkWF4miD9A7i+eM894ySUEK+rJcks4EBd08nBsLiNHPhqSasLAPX09Aqzfom/exb3+vbG5iCa3C1tq9c05ZiCIB+tJNvvm36YW5eGBfjycVIuEpasz8Fe2yjLoq9FoD47cH7EuXBvfUyb3dZYfRRYZqGkNKUjlUqP1hhPQffdpnG725wAX+YlxMDhFMwuCpRBCQQHyAEipoDaN/kkxaZmcWQdb+dODDVCev6hVF9BUR5+QLx/KNmA=
x-ms-exchange-transport-forked: True
Content-ID: <36132B01B7D1224D835506069939245B@namprd02.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 90366eac-fd7a-4124-8071-08d79a9185fc
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jan 2020 14:36:50.4101 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fa7b1b5a-7b34-4387-94ae-d2c178decee1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /tTPPGeoiafWWeMUM1r9FwnbfogiDfJjAphfUxj/QjN7C0osnfiNJxIeJEPyemVykDXjivNQe6gcF0A/a/A2uw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR02MB6656
Subject: Re: [rfc-i] No, constraining to a custom SVG profile is not trivial
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>
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>

Have you folks looked at the SVG Native proposal from the W3C - https://w3c.github.io/svgwg/specs/svg-native/index.html?

While it doesn't address all issues (like color), it should cover most/all of the other key issues that are of concern.  And it would give you a standard profile to target.

Leonard

On 1/15/20, 11:33 PM, "rfc-interest on behalf of Doug Royer" <rfc-interest-bounces@rfc-editor.org on behalf of douglasroyer@gmail.com> wrote:

    On 1/15/20 8:21 PM, Brian E Carpenter wrote:
    >> Attached is a simple XSLT script that I created that simply rips out invalid elements.
    > 
    > The problem with colour/greyscale is that this isn't enough. If you have very dark blue text on a very pale pink background, what happens? svgcheck makes this black on black; my heuristic makes it black on white. What would your script do?
    
    I use this tool with SVG files that I planned to use in this way.
    
    I have not needed to solve contrast problems yet. When I do, my plan is to make anything more than 50% black, else white.  It can not handle complex SVG with shades of darkness or complex attribute values (like style). If I get energetic, I could do some contrast computation. Never tried anything that complex with XSLT, might have to do some scripting for that.
    
    The next rev, I am going to tackle the style attribute. I do not know if it is solvable with XSLT. More of an intellectual exercise than a needed goal. If it gets complex, scripting will do.
    
    > But I do agree with Phill, this is a non-trivial issue. Currently I think doing new drawings with a simple tool like DIA is the only practical way.
    
    Yea, DIA and the DOT tools just make stick drawings. You can make nice flow and protocol state drawings with the dot tools (and with PIC for those of you that are troff experts).
    
    
    -- 
    Doug Royer - (https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2FDougRoyer.US&amp;data=02%7C01%7Clrosenth%40adobe.com%7Ce472955bdf344aea564908d79a3d3c1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637147460109168558&amp;sdata=j7fkjiq8qMlb1bCvQ98ghu5eHBCgj5kMwsZkE7%2FvAK0%3D&amp;reserved=0)
    Douglas.Royer@gmail.com
    714-989-6135
    _______________________________________________
    rfc-interest mailing list
    rfc-interest@rfc-editor.org
    https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fmailman%2Flistinfo%2Frfc-interest&amp;data=02%7C01%7Clrosenth%40adobe.com%7Ce472955bdf344aea564908d79a3d3c1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637147460109168558&amp;sdata=Xtc2yOwAhqL7PTOoy2tq8tZ8%2BFSkRFGaejcf73m2ujM%3D&amp;reserved=0
    

_______________________________________________
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