[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Why does export of images to LaTeX requires either org-special-b
From: |
Achim Gratz |
Subject: |
Re: [O] Why does export of images to LaTeX requires either org-special-blocks or org-jsinfo? |
Date: |
Wed, 21 Nov 2012 16:16:06 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) |
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