emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: gerard.vermeulen@posteo.net
Cc: Christian Moe <mail@christianmoe.com>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-html.el: add option to embed SVG for CSS support in SVG
Date: Thu, 15 Jun 2023 21:55:22 +0700	[thread overview]
Message-ID: <a20045fe-e144-7545-6eb9-e0cdb2508976@gmail.com> (raw)
In-Reply-To: <e075983f1ba2e16147d8b81008465aeb@posteo.net>

On 15/06/2023 20:09, gerard.vermeulen@posteo.net wrote:
> ;;    - For each SVG link by means of "#+ATTR_HTML: :svg-as-object t"
> ;;      or "#+ATTR_HTML: :svg-inclusion t".

Is there any advantages of using separate boolean attributes instead of 
multiple values?

- :svg object
- :svg img
- :svg dom (or any other value for inserting contents of SVG files into 
HTML)

"inline" is really ambiguous here since it may mean CSS display property 
block vs. inline that is similar to Org's block-level elements and 
inline objects.

Has anybody compared memory footprint of a document with multiple SVG 
images rendered by a browser with <img> vs <object> strategies? It seems 
at least Firefox may create frames for each <object> so the page may be 
rather heavy.


  reply	other threads:[~2023-06-15 14:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 13:23 [PATCH] ox-html.el: add option to embed SVG for CSS support in SVG gerard.vermeulen
2023-06-06  7:49 ` Ihor Radchenko
2023-06-06  9:57   ` Christian Moe
2023-06-06 13:37     ` gerard.vermeulen
2023-06-06 18:54       ` Christian Moe
2023-06-07  8:43         ` Ihor Radchenko
2023-06-07  8:41     ` Ihor Radchenko
2023-06-07 14:30       ` Christian Moe
2023-06-07 17:57         ` Ihor Radchenko
2023-06-15 13:09           ` gerard.vermeulen
2023-06-15 14:55             ` Max Nikulin [this message]
2023-06-15 20:42               ` Ihor Radchenko
2023-06-15 20:51             ` Ihor Radchenko
2023-06-16 18:39               ` gerard.vermeulen
2023-06-17 12:38                 ` Ihor Radchenko
2023-06-17 14:45                   ` gerard.vermeulen
2023-06-21 15:52               ` Max Nikulin
2023-06-21 16:02                 ` Ihor Radchenko
2023-06-21 16:27                   ` Max Nikulin
2023-06-21 16:38                     ` Ihor Radchenko
2023-06-22 16:25                       ` Max Nikulin
2023-06-23 11:02                         ` Ihor Radchenko
2023-06-06 12:58   ` gerard.vermeulen
2023-06-07  9:07     ` Ihor Radchenko
2023-06-06 14:14 ` Max Nikulin
2023-06-06 16:08   ` gerard.vermeulen
2023-06-07  9:10     ` Ihor Radchenko
2023-06-09 15:27     ` Max Nikulin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a20045fe-e144-7545-6eb9-e0cdb2508976@gmail.com \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gerard.vermeulen@posteo.net \
    --cc=mail@christianmoe.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).