From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: extra paragraph in image export?
Date: Tue, 24 Jan 2017 10:40:32 +0100 [thread overview]
Message-ID: <87sho8ztgv.fsf@gmx.us> (raw)
In-Reply-To: 87lgu3b5c8.fsf@nicolasgoaziou.fr
Hi,
>> with org-html-html5-fancy is non-nil, images are exported with something
>> like this code:
>>
>> <figure>
>> <p><img src="https://imgs.xkcd.com/comics/proof_2x.png" alt="proof_2x.png"
>> class="fragment (appear) visible current-fragment"
>> data-fragment-index="0"></p>
>> </figure>
I'm not an expert of HTML either. However, the "p" tag inside the
"figure" is uncommon looking a bit on the example usages online. Thus, I
agree with Matt that it should probably not be there.
> I'm not well-versed enough in HTML to answer this, but, from Org POV,
> there should be a difference between
>
> A paragraph
>
> #+caption: foo
> [[block-image.png]]
>
> Another paragraph
>
>
> and
>
> A paragraph with an [[inline-image.png]] and some text following.
>
> Would removing the <p> tag blur the difference between the two examples
> above ?
(I hope I understand your concern correctly).
AFAIK, the CSS selector still differs so on the output side they are not
alike. I.e. the former is "figure>img" the other is a "p>img". Aside: If
anything, removing the "p" tag inside the figure would make it easier to
handle images.
Rasmus
--
Vote for proprietary math!
next prev parent reply other threads:[~2017-01-24 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 16:26 extra paragraph in image export? Matt Price
2017-01-21 23:09 ` Matt Price
2017-01-22 13:18 ` Nicolas Goaziou
2017-01-24 9:40 ` Rasmus [this message]
2017-01-24 21:27 ` Nicolas Goaziou
2017-01-25 3:57 ` Matt Price
2017-01-25 4:04 ` Matt Price
2017-01-25 13:13 ` Nicolas Goaziou
2017-01-25 14:59 ` Rasmus
2017-01-25 15:01 ` Rasmus
2017-01-25 16:59 ` Nicolas Goaziou
2017-01-25 18:02 ` Matt Price
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=87sho8ztgv.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
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).