emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?
Date: Wed, 21 Nov 2012 14:40:34 +0100	[thread overview]
Message-ID: <20121121134034.GA31515@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87ip8zbb5o.fsf@somewhere.org>

On Wed, Nov 21, 2012 at 09:41:39AM +0100, Francesco Pizzolante wrote:
> Hi,
> 
> I have noticed that the correct export of images in LaTeX requires one of
> these 2 packages: org-special-blocks or org-jsinfo.
> 
> While I cannot see any relation between these packages and the export of
> images in LaTeX, if none of these 2 packages is loaded then images are
> exported as \href instead of \includegraphics, in other words, as links
> instead of images.
> 
> Here's the code I used to check this:
> 
>     ╭────
>     │ (setq org-modules nil)
>     │ ;;(require 'org-special-blocks)
>     │ ;;(require 'org-jsinfo)
>     ╰────
> 
> Please let me know if you have any explanation to this behaviour.
> 

Those modules are optional.  How do you write your links in the org
file?  To be included in LaTeX export with includegraphics, the
description part of the link should be empty.  e.g.

  [[/path/to/image]]

This creates an inline image in the final pdf.  You can add a caption by
adding a caption line like this:

  #+CAPTION: Some caption

If you add a caption, then the image is enclosed in a floating
environment (figure in this case).

For details see the manual: (info "(org) Images in LaTeX export")

HTH

-- 
Suvayu

Open source is the future. It sets us free.

next prev parent reply	other threads:[~2012-11-21 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  8:41 Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo? Francesco Pizzolante
2012-11-21 13:40 ` Suvayu Ali [this message]
     [not found]   ` <20121121134034.GA31515-nvtJ+N3H+Ig9gPbrd+1kzlEPDqVayaqo@public.gmane.org>
2012-11-21 14:37     ` Francesco Pizzolante
2012-11-21 15:16       ` Achim Gratz
     [not found]         ` <87pq37c7gp.fsf-9O0xPIFIXLULmYpASZe/Uw@public.gmane.org>
2012-11-21 16:04           ` 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=20121121134034.GA31515@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --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

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