Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?

Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?

[Francesco Pizzolante]

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.

Thanks a lot.

Regards,
 Francesco

Re: Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?

[Suvayu Ali]

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.

Re: Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?

[Francesco Pizzolante]

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

Re: Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?

[Achim Gratz]

Francesco Pizzolante writes:
> 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 don't do that…

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

Both of these will load org-html, either directly or indirectly.  With
that the default definition for org-export-html-inline-images comes into
existence, which despite the name is also used for other exporters.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo?

[Francesco Pizzolante]

Hi Achim,

> Both of these will load org-html, either directly or indirectly.  With
> that the default definition for org-export-html-inline-images comes into
> existence, which despite the name is also used for other exporters.

Thanks a lot for the explanation.

Is there a plan to make this variable independent of the html backend?

Regards,
 Francesco