emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Darlan Cavalcante Moreira <darcamo@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>,
	emacs-orgmode@gnu.org,
	"Carsten Dominik" <carsten.dominik@gmail.com>
Subject: Re: Re: LaTeX export of images
Date: Fri, 02 Oct 2009 11:23:20 -0400	[thread overview]
Message-ID: <31946.1254497000@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Darlan Cavalcante Moreira <darcamo@gmail.com> of "Fri, 02 Oct 2009 10:04:59 -0300." <4ac5fa81.47c2f10a.45ee.0746@mx.google.com>

Darlan Cavalcante Moreira <darcamo@gmail.com> wrote:

> At Fri, 2 Oct 2009 08:55:22 +0200,
> Carsten Dominik wrote:
> > Do we need to implement a way so that text can be made to flow around  
> > a figure, just as it is possible in HTML export?  What would be the  
> > right LaTeX package to use for this purpose?
> > 
> The Latex wikibook
> http://en.wikibooks.org/wiki/LaTeX/Floats,_Figures_and_Captions#Wrapping_text_around_figures
> suggests the wrapfigure package, but it also warns that some manual adjustments
> is often required. Therefore, if this is implemented in the latex exporter it is
> probably a good idea to provide options to include latex commands that will be
> put before and after the \includegraphics command. See the example in the
> section "Tip for figures with too much white space" of the wikibook where some
> \vspace were used to adjust white space around the figure.
> 

... and the TeX FAQ seems to agree that wrapfig is probably the best option:

    http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textflow

It also mentions some additional limitations.

Nick

  reply	other threads:[~2009-10-02 16:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 13:39 LaTeX export of images Francesco Pizzolante
     [not found] ` <87pr9jf68i.fsf-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
2009-09-23 14:04   ` Sébastien Vauban
2009-09-23 15:30     ` Jeff Kowalczyk
2009-09-23 21:09       ` Sébastien Vauban
2009-09-29  9:30         ` Carsten Dominik
2009-10-02  6:55         ` Carsten Dominik
2009-10-02 13:04           ` Darlan Cavalcante Moreira
2009-10-02 15:23             ` Nick Dokos [this message]
2009-10-03  7:05               ` Carsten Dominik
2009-10-05 14:19                 ` Darlan Cavalcante Moreira
     [not found]                 ` <B2499F80-4D9D-4F76-9432-ACF04E38C8EE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-10-13 10:03                   ` Francesco Pizzolante
2009-10-20 10:18                     ` Carsten Dominik
2009-09-29  9:28 ` Carsten Dominik
2009-09-29 19:32   ` Nick Dokos
2009-09-30  7:30     ` Carsten Dominik
     [not found]     ` <8809.1254252762-/Z0n3E7Cx4uRQBexplnFlPegYHeGw8Jk@public.gmane.org>
2009-09-30  8:53       ` Francesco Pizzolante

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=31946.1254497000@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=carsten.dominik@gmail.com \
    --cc=darcamo@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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).