emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: alban bernard <alban.bernard@yahoo.fr>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: resize multiple image within a row or paragraph
Date: Wed, 24 Sep 2014 15:37:17 +0200	[thread overview]
Message-ID: <m2fvfhxhpu.fsf@christianmoe.com> (raw)
In-Reply-To: <87r3z3lkdl.fsf@nicolasgoaziou.fr>


Nicolas Goaziou writes:
> Hello,
>
> Christian Moe <mail@christianmoe.com> writes:
>
>> Here's a simple CSS workaround that might or might not work well for
>> you, and won't work for non-HTML backends, but at least requires minimal
>> hacking: 
>
> [...]
>
> Good to know.
>
> Anyhow, does my proposal make sense?
>
>
> Regards,

Hi,

Sorry, catching up on mail. Also, I misunderstood your proposal when you
wrote it -- I thought it was a suggestion for what the user could
do. But now I realize it's a proposed change to the HTML backend
itself. You wrote:

> `html' back-end can redefine what
> a paragraph is, instead of following Org's own definition. More
> explicitly, an HTML paragraph can be defined as a cluster of elements
> not separated by any blank line and containing at least an Org
> paragraph. Hence:

>   #+attr_html: :width 10%
>   [[./img1.png]]
>   Paragraph
>   #+attr_html: :width 10%
>   [[./img2.png]]

> consists of two paragraphs in Org, but would be seen as a single
> paragraph by HTML, and exported as such.

> Implementation is simple using pseudo-elements. `latex' back-ends does
> it already for tables and math snippets. However, I'm no HTML
> specialist, so there may be drawbacks I cannot foresee.

I'm no expert either. But FWIW, it does make sense to me, and seems
intuitive from an HTML-centric view, since IMG elements
in HTML are basically inline. I think users would expect to have to put
blank lines around an image if they want it wrapped in a paragraph, and
should expect to get in trouble if they did not put blank lines around a
captioned figure.

Yours,
Christian

      reply	other threads:[~2014-09-24 13:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18 15:13 resize multiple image within a row or paragraph alban bernard
2014-09-20  7:23 ` alban bernard
2014-09-20 12:08   ` Nicolas Goaziou
2014-09-21 13:22     ` alban bernard
2014-09-21 18:08       ` Christian Moe
2014-09-21 19:02         ` alban bernard
2014-09-22 15:56         ` Nicolas Goaziou
2014-09-24 13:37           ` Christian Moe [this message]

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=m2fvfhxhpu.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=alban.bernard@yahoo.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).