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

From: "Francesco Pizzolante" <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
To: Suvayu Ali <fatkasuvayu+linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?
Date: Wed, 21 Nov 2012 15:37:24 +0100	[thread overview]
Message-ID: <87y5hvt42j.fsf@somewhere.org> (raw)
In-Reply-To: <20121121134034.GA31515-nvtJ+N3H+Ig9gPbrd+1kzlEPDqVayaqo@public.gmane.org> (Suvayu Ali's message of "Wed, 21 Nov 2012 14:40:34 +0100")

Hi Suvayu,

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

That's exactly what I do and it works perfectly until you do this (trying to
load as few modules as possible):

    ╭────
    │ (setq org-modules nil)
    ╰────

Then, you'll see that images will be exported as links instead of images
(\href instead of \includegraphics).

What I don't understand is that you fix the issue by loading either
org-special-blocks or org-jsinfo (uncommenting one of these 2 lines):

    ╭────
    │ (require 'org-special-blocks)
    │ ;;(require 'org-jsinfo)
    ╰────

Thus, it seems like these packages are not optional (or, at least, of the 2)
to get the correct export of inline images to LaTeX.

Any idea why this behavior?

Regards,
 Francesco

next prev parent reply	other threads:[~2012-11-21 14:37 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
     [not found]   ` <20121121134034.GA31515-nvtJ+N3H+Ig9gPbrd+1kzlEPDqVayaqo@public.gmane.org>
2012-11-21 14:37     ` Francesco Pizzolante [this message]
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=87y5hvt42j.fsf@somewhere.org \
    --to=fpz-djc/ipccudyqhejpep6iedvlejwurmry@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    --cc=fatkasuvayu+linux-Re5JQEeQqe8AvxtiuMwx3w@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

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