From: Bastien <bzg@gnu.org>
To: Rick Frankel <rick@rickster.com>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [RFC] <img> vs <object> in HTML export
Date: Sat, 11 Jan 2014 10:21:39 +0100 [thread overview]
Message-ID: <87y52mzxek.fsf@bzg.ath.cx> (raw)
In-Reply-To: <cf32d8f09aa9412b50e9369e0471da9d@mail.rickster.com> (Rick Frankel's message of "Fri, 10 Jan 2014 11:09:59 -0500")
Rick Frankel <rick@rickster.com> writes:
> I thing the solution is to use an <object> tag for svg, but an <img>
> tag for the rest.
Yes -- I'm no HTML guru, but this corresponds to what I see in most
HTML pages.
--
Bastien
next prev parent reply other threads:[~2014-01-11 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 21:10 [RFC] <img> vs <object> in HTML export Nick Dokos
2014-01-10 16:09 ` Rick Frankel
2014-01-10 19:12 ` Nick Dokos
2014-01-11 9:21 ` Bastien [this message]
2014-01-16 22:45 ` Rick Frankel
2014-01-16 23:18 ` Nick Dokos
2014-01-17 0:44 ` Nicolas Goaziou
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=87y52mzxek.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
--cc=rick@rickster.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).