From: Max Nikulin <manikulin@gmail.com>
To: gerard.vermeulen@posteo.net
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-html.el: add option to embed SVG for CSS support in SVG
Date: Wed, 21 Jun 2023 23:27:16 +0700 [thread overview]
Message-ID: <1f6df732-67ee-b100-82f6-248edbddbcf3@gmail.com> (raw)
In-Reply-To: <87zg4sdcrq.fsf@localhost>
On 21/06/2023 23:02, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>>> I think you missed `org-html-inline-image-rules' where users can
>>> include/exclude svg images from inlining.
>>
>> Ihor, I am not sure that I get your point. If I understand it correctly,
>> `org-html-inline-image-rules' specifies whether links to svg files
>> should be kept as links or should be transformed to images. Gerard
>> proposes to add options how to treat SVG *images*: <img>, <object> or
>> include content of the SVG file literally. `org-html-inline-image-rules'
>> does not allow to specify extended options how to treat each match.
>
> That's why Timothy should review this patch.
> I am missing all these subtle details about HTML due to lack of knowledge.
Besides the HTML related question how to mate all SVG options with all
Org features (figures, etc.) there is a purely Org design choice:
whether there should be multiple Org boolean variables and attributes
describing strategy for particular image or it is single variable and
attribute with symbol (or string) value.
next prev parent reply other threads:[~2023-06-21 16:28 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
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 [this message]
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=1f6df732-67ee-b100-82f6-248edbddbcf3@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gerard.vermeulen@posteo.net \
/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).