On 08/26/2015 02:06 PM, Rasmus wrote:
Hi Scott,
Thanks for your bug report.
Scott Randby <sran...@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.
I don't use the git repository for Org, so I'll just have to leave that
question unanswered.
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).
I don't really have the technical knowledge required to address the
issue. The configuration option is the best option in my view. One
option allows SVGs to be handled the old way and the other the new way.
Perhaps something like this:
#+ATTR_HTML: :svg img
or
#+ATTR_HTML: :svg object
In my view, the default should be img, but I intend for my pages to be
viewed by browsers which support SVG images. I direct my students to
those browsers. Also, the W3C draft document states that support for SVG
via the <img> tag is the desired solution.
I will experiment a bit to see if I can get the <object> tag solution
working for me. But given the short amount of time I have to get my
pages up (by Sunday), I will probably put the desired HTML code into the
Org file directly until the issue is resolved.
Scott
