From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Scaling HTML-exported SVG
Date: Sun, 24 Jul 2016 21:48:12 +0300 [thread overview]
Message-ID: <878twqq3df.fsf@iki.fi> (raw)
In-Reply-To: 87y44qdipu.fsf@iki.fi
Jarmo Hurri <jarmo.hurri@iki.fi> writes:
> Christian Moe <mail@christianmoe.com> writes:
>> #+html_head_extra: <style>#svgfig {width: 200px; }</style>
>>
>> #+attr_html: :id svgfig
>> [[path/to/image.svg]]
>>
>> For this to work, the SVG needs to be written to be scalable (with
>> viewport set etc.).
>
> (Also addressed this in the other thread; also here for completeness.)
>
> But this means scaling on a file-by-file basis, which is very
> inconvenient for any larger projects.
Did some tests.
The method you suggested above - setting id - works (all tests done in
Chrome). But setting id-values is cumbersome, because you need to do it
for every file.
It is also possible to set a CSS class similarly, that is, modifying
your example above,
#+html_head_extra: <style>.svgfig {width: 200px; }</style>
#+attr_html: :class svgfig
[[path/to/image.svg]]
This also works and is better, because then it is possible to set a
common class for all SVG figures, and handle them with a single CSS
rule. Better, but not yet perfect, because I still need to add a
attr_html to every SVG figure.
But there seems to be a way around this. With the last approach the
generated HTML looks something like
<object type="image/svg+xml" data="image.svg" class="svgfig">
Why don't we just set a common class for all SVG-images in an HTML
export by default? Then we could still use an <object> to embed it, and
control its size from CSS.
It seems to me that this solves the problem, and requires an extremely
small change.
Jarmo
next prev parent reply other threads:[~2016-07-24 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 13:10 Scaling HTML-exported SVG Jarmo Hurri
2016-07-24 17:09 ` Christian Moe
2016-07-24 17:55 ` Jarmo Hurri
2016-07-24 18:48 ` Jarmo Hurri [this message]
2016-07-24 21:26 ` Christian Moe
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=878twqq3df.fsf@iki.fi \
--to=jarmo.hurri@iki.fi \
--cc=emacs-orgmode@gnu.org \
/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).