From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114902 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Thangalin via ntg-context Newsgroups: gmane.comp.tex.context Subject: Re: SVG style ignored after double semicolon Date: Mon, 9 May 2022 16:17:23 -0700 Message-ID: References: <85A94842-FECF-454B-BFD0-B13EFF4C2786@me.com> Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0770562026855949546==" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36580"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Thangalin To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Tue May 10 01:18:46 2022 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane-mx.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1noCeM-0009Fw-Nv for gctc-ntg-context-518@m.gmane-mx.org; Tue, 10 May 2022 01:18:46 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id C4760360721; Tue, 10 May 2022 01:17:40 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyM3EJlCajNF; Tue, 10 May 2022 01:17:39 +0200 (CEST) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 36F14360730; Tue, 10 May 2022 01:17:39 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 41C7C36072B for ; Tue, 10 May 2022 01:17:37 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q-lT6KbNz-EA for ; Tue, 10 May 2022 01:17:36 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.208.179; helo=mail-lj1-f179.google.com; envelope-from=thangalin@gmail.com; receiver= Original-Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 50917360721 for ; Tue, 10 May 2022 01:17:36 +0200 (CEST) Original-Received: by mail-lj1-f179.google.com with SMTP id t25so18857166ljd.6 for ; Mon, 09 May 2022 16:17:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=S2RstCUkCZwWqJsyrKAjHSLILyWWpkbG1u+ylUoRsAQ=; b=NO0fYb2gZVSfVxQMtMW6cCou8J2YeBEnrzpY9sEIMgeeh6WdNFb7Wsf1sqOpgtgUrh WLSYa3CAyKPT+NGegG3jMQ4th4xWuJWhnCYBEEI0G8QHxxZ6JL9zaWX80ESHQv0S1u06 7MQuVw2eRGKJqlmGpEsuuxcmRV/Y+0Fq3adZ+uUyS93Jl+i4vi5OmVNqa1hvTVDuFP4E wpUsSw4+XoKi3spkagHoFLo2EqxNWN0VUgEC9dLFKO6GbFYdEZcpYykYlN+Tr+2fklio XayWDPKFk3B8n9ZHx4aPTDMdNPMwRjXo2XqwVVupni0YUL8KgcsWUkawjJPXuxH/tBnR FsCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=S2RstCUkCZwWqJsyrKAjHSLILyWWpkbG1u+ylUoRsAQ=; b=fVv9sz67SlJPYpO0dCCapvp2pX+kKAEi0dfSJQI7tE2eeAGcQtfaC99Gso44Ym6Hnx yuVnsd/AufbZUa2MVOaM4u/PfVMJ9zdw6W08fx+DcgrQ5+ZPKRV9UUYRpgCyT3Tdl3O6 jBIsJYW8q+TrlPacCVCAHYNT9bSBgzGZzxwYyJqojclcOt3ohiSLF5OCL2GrPty15tPc 24rBi2Shn1a0SxfTcouu9pmtocMQXIqnhWB43oJCLAVXlihVEDTE3P0nXt9pKERSvwD2 bCWrHAYsuJXbJdLlQCAh4rgTAhA4HVjQcF/ceApqaMmpac5/8Rk8kiSjZYbwoDjojgM3 X5UA== X-Gm-Message-State: AOAM531RC9juMuKgoxGfMq1A9V8JiFVLA7HbUhy7qA2+KMnBYH3jogI8 egcT1AwWD+scP26ergb5BRuaUm1H0b/VsG5BnM67670jvNc= X-Google-Smtp-Source: ABdhPJypJDAFhBlwNGa/BN3MfCbTCcnhywjprVA3MILozPyS69/Y3Wiz9JbE7i5r3TGgk7hpSVapLShHKazvrQcBRl4= X-Received: by 2002:a2e:978c:0:b0:250:8db3:d1cc with SMTP id y12-20020a2e978c000000b002508db3d1ccmr12282763lji.370.1652138254547; Mon, 09 May 2022 16:17:34 -0700 (PDT) In-Reply-To: X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.io gmane.comp.tex.context:114902 Archived-At: --===============0770562026855949546== Content-Type: multipart/alternative; boundary="000000000000c83f3b05de9c6969" --000000000000c83f3b05de9c6969 Content-Type: text/plain; charset="UTF-8" That's another good idea Heinrich. I certainly could invoke another application to sanitize the SVG, but that brings with it a number of additional problems: Does the user have it installed properly? Is it cross-platform? Additionally, the typesetting code (in Java) would have to be updated to call out to sanitize the file, plus introducing more error handling for when sanitizing goes wrong. Cleaning up the input document feels more like a band-aid than solving the underlying problem, which is to relax the regex ConTeXt uses to parse the style attribute. I'm pretty sure I can provide a patch for the regex, I just need to know how to get debugging information printed to the console when compiling the document using the context command. Any ideas about how to log strings after modifying mlib-svg.lmt? I tried adding print/report statements, but none of them showed up. Does anyone know if that's even the right file to change to start looking into the issue? Thanks again! --000000000000c83f3b05de9c6969 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That's another good idea Heinrich.

=
I certainly could invoke another application to sanitize the SVG= , but that brings with it a number of additional problems: Does the user ha= ve it installed properly? Is it cross-platform? Additionally, the typesetti= ng code (in Java) would have to be updated to call out to sanitize the file= , plus introducing more error handling for when sanitizing goes wrong. Clea= ning up the input document feels more like a band-aid than solving the unde= rlying problem, which is to relax the regex ConTeXt uses to parse the style= attribute.

I'm pretty sure I can provide = a patch for the regex, I just need to know how to get debugging information= printed to the console when compiling the document using the context comma= nd.

Any ideas about how to log strings after modif= ying mlib-svg.lmt? I tried adding print/report statements, but none of them= showed up. Does anyone know if that's even the right file to change to= start looking into the issue?

Thanks again!
--000000000000c83f3b05de9c6969-- --===============0770562026855949546== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg== --===============0770562026855949546==--