From: Achim Gratz <Stromeko@nexgo.de>
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 16:16:06 +0100 [thread overview]
Message-ID: <87pq37c7gp.fsf@Rainer.invalid> (raw)
In-Reply-To: 87y5hvt42j.fsf@somewhere.org
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
next prev parent reply other threads:[~2012-11-21 15:16 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
2012-11-21 15:16 ` Achim Gratz [this message]
[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=87pq37c7gp.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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
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).