emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Inline Images Export Bug
Date: Wed, 26 Aug 2015 20:06:59 +0200	[thread overview]
Message-ID: <876141apq4.fsf@gmx.us> (raw)
In-Reply-To: 55DDFCBF.2050202@gmail.com

Hi Scott,

Thanks for your bug report.

Scott Randby <srandby@gmail.com> writes:

> When did Org start using the <object> tag for inline image HTML
> export?

You should use git-blame to find out if you care.


> The problems with the second bit of exported code is that it doesn't
> scale the image to fit the block with 50% width (only a small part of
> the image is visible), and you when you right click on the image, you
> can't view it, save it or anything.
>
> [...]
> 
> Clearly, Org 8.3 is not using an <img> tag when exporting SVG images
> to HTML, something which is a major issue for me. It essentially makes
> Org unusable for HTML export. I really would appreciate a fix for this
> bug.

I'm not sure it's a bug.  It's IS clearly a quite complicated issue, e.g.:

    http://stackoverflow.com/questions/4476526/do-i-use-img-object-or-embed-for-svg-files

Perhaps it should be configurable, perhaps even as a default and a
per-image basis (via #+attr_html).

If you can provide a (html) solution that takes into consideration the
issues mentioned on SO that would of course be great.  In the age of d3.js
interactivity COULD be an issue (I would always load "interactive svgs"
via JS, but I'm a pretty naïve svg user so I don't know what's possible).

Rasmus

-- 
Together we'll stand, divided we'll fall

next prev parent reply	other threads:[~2015-08-26 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 17:51 Inline Images Export Bug Scott Randby
2015-08-26 18:06 ` Rasmus [this message]
2015-08-26 19:26   ` Scott Randby
2015-08-26 22:35     ` Rasmus
2015-08-26 23:06       ` Scott Randby
2015-08-26 19:39   ` Pip Cet
2015-08-26 21:56     ` Rasmus
2015-08-26 22:40       ` Pip Cet
2015-08-26 23:13         ` Scott Randby
2015-08-26 19:50   ` Scott Randby
2015-08-27  1:35 ` Nick Dokos

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=876141apq4.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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

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).