emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: LaTeX export of images
Date: Wed, 23 Sep 2009 23:09:42 +0200	[thread overview]
Message-ID: <878wg5mkq1.fsf@mundaneum.com> (raw)
In-Reply-To: loom.20090923T172940-728@post.gmane.org

Jeff Kowalczyk wrote:
> Sébastien Vauban <wxhgmqzgwmuf@...> writes:
>> Francesco Pizzolante wrote:
>>> In this case, we should just generate \includegraphics{myimage} without
>>> the centerline command.
>>
>> Given the output of the `\centerline' command, I guess that the inlining of
>> an image inside a line of text is not supported as is by Org. I can second
>> such a choice.
>
> +1 for default to inline graphics. When using Org for How-To and project
> documentation delivered as PDF, floating screenshot-size images typically
> situate far from the descriptive text.

My point was mainly that, IMHO, floating or not should not be tied to the
presence or absence of caption/label.

Your problem with screenshots far away should be solved by putting the H
specifier to the float environment and loading the `float' package.


> I would prefer inline images by default (or option), and a file/subtree
> level option to use LaTeX floating layout.

That'd be a great way to be able to specify which type of "inlining" we want.
On a per file basis seems sufficient for me.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-09-23 21:09 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 [this message]
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
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=878wg5mkq1.fsf@mundaneum.com \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).