From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Price Subject: Bug? svg images do not display on modenr browser on export Date: Tue, 15 Jan 2019 18:50:45 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000aa0ab6057f87d347" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gjYTn-00043O-47 for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 18:50:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gjYTf-0004R8-4K for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 18:50:40 -0500 Received: from mail-io1-xd2c.google.com ([2607:f8b0:4864:20::d2c]:46123) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gjYTb-0004Ku-3o for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 18:50:35 -0500 Received: by mail-io1-xd2c.google.com with SMTP id v10so3484566ios.13 for ; Tue, 15 Jan 2019 15:50:33 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Org Mode --000000000000aa0ab6057f87d347 Content-Type: text/plain; charset="UTF-8" I think this is a bug but I don't know enough about svg images to be sure. On export, links to svg images produce an element rather than an . Here's the docstring of the function (from ox-heml): ----- Return \"object\" embedding svg file SOURCE with given ATTRIBUTES. INFO is a plist used as a communication channel. The special attribute \"fallback\" can be used to specify a fallback image file to use if the object embedding is not supported. CSS class \"org-svg\" is assigned as the class of the object unless a different class is specified with an attribute. ------- Neither chrome nor firefox can display these objects. On the other hand, if I modify ~org-html--format-image to~ treat svg images just like other images (in an tag) then the image displays just fine. Is there a reason we use the object tag instead/ If not, what's the best solution? I na try to work on a proper fix. Thanks, Matt --000000000000aa0ab6057f87d347 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think this is a b= ug but I don't know enough about svg images to be sure.=C2=A0 On export= , links to svg images produce an <object> element rather than an <= img>.=C2=A0 Here's the docstring of the function (from ox-heml):

-----
Return \"object\" = embedding svg file SOURCE with given ATTRIBUTES.
INFO is a plist used as= a communication channel.

The special attribute \"fallback\&quo= t; can be used to specify a
fallback image file to use if the object emb= edding is not
supported.=C2=A0 CSS class \"org-svg\" is assign= ed as the class of the
object unless a different class is specified with= an attribute.
-------
Neither chrome nor firefox can d= isplay these objects.=C2=A0 On the other hand, if I modify ~org-html--forma= t-image to~ treat svg images just like other images (in an <img> tag)= then the image displays just fine.=C2=A0 Is there a reason we use the obje= ct tag instead/ If not, what's the best solution? I na try to work on a= proper fix.

Thanks,
Matt
=
--000000000000aa0ab6057f87d347--