emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>,
	emacs-orgmode@gnu.org, Eric Schulte <eric.schulte@gmx.com>
Subject: Re: [ODT] image scaling overridden by long caption
Date: Tue, 24 Jan 2012 01:23:40 +0530	[thread overview]
Message-ID: <81ipk2mbzv.fsf@gmail.com> (raw)
In-Reply-To: <87r4yt9x5u.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Sat, 21 Jan 2012 11:18:05 +0100")

[-- Attachment #1: Type: text/plain, Size: 2572 bytes --]

Hello Andreas

I have added support for character anchored images as part of the
following commit release_7.8.03-201-g1d99fd7.

I am attaching a sample Org file and the associated ODT output.

Don't be surprised. Please Read on ...

--8<---------------cut here---------------start------------->8---
#+TITLE:     side-by-side.org
#+AUTHOR:    Jambunathan K
#+EMAIL:     kjambunathan@gmail.com
#+DATE:      2012-01-23 Mon
#+OPTIONS:   H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS:   TeX:t LaTeX:dvipng skip:nil d:nil todo:t pri:nil tags:not-in-toc



Does the existing behaviour as captured in [[Side-by-Side images laid
out by hand]] be preserved with new export driver?


1. can the extraneous parbreaks in [[Side-by-Side images using Babel]] be
2. Can [[http://lists.gnu.org/archive/html/emacs-orgmode/2012-01/msg00678.html][this issue with #+header lines ]] be fixed?

* Side-by-Side images using Babel

Creating side-by-side images with Babel is problematic.

#+caption: foo
#+ATTR_ODT: :width 7 :height 7 :anchor as-char
#+header: :file foo.png
#+begin_src R :exports results :results graphics
  plot(1:100, 1:100)
#+caption: foo
#+ATTR_ODT: :width 7 :height 7 :anchor as-char
#+header: :file foo.png
#+begin_src R :exports results :results graphics
  plot(1:100, 1:100)

The images are vertically stacked because Babel introduces extraneous
parbreaks. This forces the images to be anchored as character, but to
*successive* paragraphs.

Here is a segment of Org buffer as seen by the ODT exporter at the end
of =org-export-preprocess-string=.

  ,Creating side-by-side images with Babel is problematic.
  ,The images are vertically stacked because Babel introduces extraneous
  ,parbreaks. This forces the images to be anchored as character, but to
  ,*successive* paragraphs.

* Side-by-Side images laid out by hand

To create side-by-side images flank them with paragraph boundaries.

#+caption: foo
#+ATTR_ODT: :width 7 :height 7 :anchor as-char
#+header: :file foo.png
#+caption: bar
#+ATTR_ODT: :width 7 :height 7 :anchor as-char
#+header: :file bar.png

You should be seeing side-by-side images.
--8<---------------cut here---------------end--------------->8---

[-- Attachment #2: side-by-side.odt --]
[-- Type: application/vnd.oasis.opendocument.text, Size: 24202 bytes --]

[-- Attachment #3: Type: text/plain, Size: 1382 bytes --]

>>> On a related note:  Could I place two (correctly scaled) images
>>> side-by-side?
>> For the sake of record, your request is much similar to what is
>> discussed here
>> http://lists.gnu.org/archive/html/emacs-orgmode/2011-12/msg00780.html -
>> save for (dynamically-generated) images taking the place of src blocks.
>> Try something like this:
>> #+begin_list-table
>> - [[./foo1.png]]
>>   - [[./foo2.png]]
>> #+end_list-table
>> Make sure that the images are "small" images. If you replace the image
>> links above with R srcblocks or attach caption/attr_odt to the above
>> above images, the results are less than satisfactory. So the answer to
>> your question is a "soft" no.
> Thanks for this.  For two reasons that does not work for me:
> (1) I want to use captions on my images
> (2) it is odt-export specific
>> Notes to self:
>> There are multiple ways to achieve side-by-side effect.
>> - use tables (aka "list tables")
>> - use 2-Column sections 
>> - 2-column frames (what is this?)
>> "side-by-side" has surfaced in the list for the second time, I think it
>> deserves to be supported "out of the box".
> +1.  And ideally generic enough, s.t. also the LaTeX supports it.
> Beamer has the concept of columns, which is nicely supported in org
> mode.  Maybe that could be a general concept supported by all (or, most)
> exporters?


  reply	other threads:[~2012-01-23 19:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  8:52 Andreas Leha
2012-01-19 20:03 ` Jambunathan K
2012-01-21 10:18   ` Andreas Leha
2012-01-23 19:53     ` Jambunathan K [this message]
2012-01-23 21:20       ` Nicolas Goaziou
2012-02-01  9:16         ` comments and attributes Jambunathan K
2012-02-01 13:04           ` Nicolas Goaziou
2012-02-15  0:03       ` [ODT] image scaling overridden by long caption Andreas Leha
2012-01-27 14:40     ` Jambunathan K
2012-01-27 22:41       ` Andreas Leha
2012-01-31  4:59         ` Jambunathan K
2012-02-07 10:04           ` Andreas Leha
2012-01-23  1:53   ` Side-by-side support (was:Re: [ODT] image scaling overridden by long caption) Christian Wittern
2012-01-23 16:34     ` Side-by-side support Jambunathan K
2012-01-23 23:51       ` Christian Wittern

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:

  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=81ipk2mbzv.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.schulte@gmx.com \
    --cc=n.goaziou@gmail.com \
    --subject='Re: [ODT] image scaling overridden by long caption' \


* 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 inbox:


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