From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Very large svg file output from latex block using =#+header: :imagemagick=
Date: Mon, 04 Nov 2013 10:39:43 +0100 [thread overview]
Message-ID: <8761s8qzds.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: CA+M2ft-6cGns4EfOy=QXhhM0AFWJUV8NDu2N6WvaGFyroetEMQ@mail.gmail.com
Hi John,
John Hendy <jw.hendy@gmail.com> writes:
> I'm trying to following along with the example here:
> - http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html#sec-4-3
>
> I don't need dual export, so I tried this instead for straight html
> compatible output:
>
> #+header: :file tree.svg
> #+header: :imagemagick
> #+begin_src latex
> \usetikzlibrary{trees}
> \begin{tikzpicture}
> \node [circle, draw, fill=red!20] at (0,0) {1}
> child { node [circle, draw, fill=blue!30] {2}
> child { node [circle, draw, fill=green!30] {3} }
> child { node [circle, draw, fill=yellow!30] {4} }};
> \end{tikzpicture}
> #+end_src
>
> Should this work? I get this error:
>
> org-babel-execute:latex: Can not create svg files, please specify a
> .png or .pdf file or try the :imagemagick header argument
>
> In perusing another thread, it looks like the argument might be
> =:imagemagic yes=?
> - http://lists.gnu.org/archive/html/emacs-orgmode/2011-02/msg01302.html
>
> When I do that and run the above, I get a 30.9mb file as the .svg
> output. Surely I'm doing something incorrectly?
Well, the error message is misleading.
If you go via imagemagick, I guess, the image is rendered and converted
to pixel graphics and then converted back to svg with embedded pixel
graphics, which will inflate the output.
The way to go is to customize org-babel-latex-htlatex to "htlatex".
Then, the block without the :imagemagick header argument should produce
a decent svg.
For reference, this works for me (having org-babel-latex-htlatex set to
"htlatex")
--8<---------------cut here---------------start------------->8---
#+header: :file tree.svg
#+header: :results file raw
#+begin_src latex
\usetikzlibrary{trees}
\begin{tikzpicture}
\node [circle, draw, fill=red!20] at (0,0) {1}
child { node [circle, draw, fill=blue!30] {2}
child { node [circle, draw, fill=green!30] {3} }
child { node [circle, draw, fill=yellow!30] {4} }};
\end{tikzpicture}
#+end_src
#+results:
[[file:tree.svg]]
--8<---------------cut here---------------end--------------->8---
Regards,
Andreas
>
> Just pulled this morning before executing:
>
> Org-mode version 8.2.1 (release_8.2.1-163-ge7397d @
> /home/jwhendy/.elisp/org.git/lisp/)
>
>
> Thanks for any suggestions!
> John
prev parent reply other threads:[~2013-11-04 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 21:31 Very large svg file output from latex block using =#+header: :imagemagick= John Hendy
2013-11-03 1:31 ` Vladimir Lomov
2013-11-04 9:39 ` Andreas Leha [this message]
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=8761s8qzds.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.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).