From: Tobias Getzner <tobias.getzner@gmx.de>
To: emacs-orgmode@gnu.org
Subject: [Bug] Errors when evaluating LaTeX source block with new SVG headers patch
Date: Mon, 22 Sep 2014 10:05:50 +0000 (UTC) [thread overview]
Message-ID: <lvos9u$n66$1@ger.gmane.org> (raw)
Evaluating LaTeX source blocks had an issue where header options would be
ignored when exporting to SVG; this appears to have been addressed in
246df88. I have patched this commit into my 8.2.7c installation. While
the headers now seem to work, I’ve noticed that LaTeX still doesn’t like
the generated temporary files when SVG-output is selected. Below is an
example which fails to work when SVG output is chosen, but which will
work when PNG is used.
#+HEADERS: :headers '("\\usepackage{tikz}" "\\usetikzlibrary
{shapes,arrows,positioning}")
#+BEGIN_src latex :file test.svg :imagemagick
\begin{tikzpicture}
\node {quux quux quux};
\end{tikzpicture}
#+END_SRC
The generated temporary LaTeX file is shown below.
\documentclass[preview]{standalone}
\def\pgfsysdriver{pgfsys-tex4ht.def}
\usepackage[usenames]{color}
\usepackage{tikz}
\usepackage{color}
\usepackage{listings}
\usepackage{amsmath}
\usepackage{tikz}
\usetikzlibrary{shapes,arrows,positioning}
\begin{document}\begin{tikzpicture}
\node {quux};
\end{tikzpicture}\end{document}
By default, LaTeX will choke on this with a lot of undefined command
errors. I have no clue about PGF, but I’ve noticed that if I insert
«\usepackage{pgf}» before the «\def\pgfsysdriver» line, this will resolve
those errors. Should this be done in ob-latex too?
After these errors are resolved, though, LaTeX will still complain about
an option clash for the color package. At first I thought this might be
because the colors package is imported twice. But apparently PGF will
also import colors, so that both the «\usepackage{pgf}» and the «\def
\pgfsysdriver» had to come after «\usepackage[usenames]{color}».
Best regards,
T.
reply other threads:[~2014-09-22 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='lvos9u$n66$1@ger.gmane.org' \
--to=tobias.getzner@gmx.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).