emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Cook, Malcolm" <MEC@stowers.org>
To: 'Aaron Ecay' <aaronecay@gmail.com>,
	'Malcolm Cook' <malcolm.cook@gmail.com>,
	"'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>,
	'Nick Dokos' <ndokos@gmail.com>,
	'Suvayu Ali' <fatkasuvayu+linux@gmail.com>,
	'Eric Schulte' <schulte.eric@gmail.com>,
	'Vincent Beffara' <vbeffara@ens-lyon.fr>,
	"'Thomas S. Dye'" <tsd@tsdye.com>,
	"'philten@cern.ch'" <philten@cern.ch>,
	'Charles Berry' <ccberry@ucsd.edu>
Subject: Re: how to handle svg files when exporting orgmode to html	and pdf?
Date: Mon, 28 Oct 2013 22:02:16 +0000	[thread overview]
Message-ID: <D4772401B9D976478C0895769BE3E792C1A968@MBSRV02.sgc.loc> (raw)
In-Reply-To: <874n8117vk.fsf@gmail.com>

Hi Aaron,

>> Can I re-open this thread to discuss two new issues I now experience with emacs 24.3.1 and orgmode version 8.2.1 in the handling of
 >svg => tex => pdf ?
 >>
 >> Here goes:
 >>
 >> 1) If the plot has text in it which contains a percent character (%),
 >> then we fail due to https://bugs.launchpad.net/inkscape/+bug/857231
 >
 >It sounds from
 ><https://bugs.launchpad.net/inkscape/+bug/719320/comments/3> as though
 >inkscape makes a deliberate effort to support LaTeX markup in their
 >pdf+latex output.  So it’s not surprising that % is a problem.
 >
>It’s unfortunate from the perspective of having a single SVG file that
 >works in both HTML and LaTeX, but I don’t know if that is an argument
 >that will cut ice with them.  I don’t know what org can/should do to
 >patch around inkscape’s design decisions.

Indeed!  So, I made a suggestion to 'fix' (?) Inkscape here:

https://bugs.launchpad.net/inkscape/+bug/719320

Let's see if I get any traction on that!

>
 >Certainly the svg LaTeX package could be patched to use inkscape’s pdf
 >export, instead of the pdf+latex one.  This would lose the nice fonts
 >that running the text through latex nets you, but get rid of the %
 >annoyances.
 >
 >>
 >> 2) If the :file is in a sub-directory  (for example, `:file
 >> fig/mtcars.svg`), even though both ./fig/mtcars.pdf_tex  and
 >> ./fig/mtcars.pdf are created, the reference to the .pdf in the
 >> .pdf_tex  is not interpreted relative to the subdirectory, but rather
 >> to the parent, and so the .pdf is not found.
 >
 >Have you looked at the \graphicspath macro from the graphics package?
 ><http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath>.  You may
 >be able to get things to work by adding \graphicspath{{fig/}} (note the
 >double braces) to your document.  \setsvg{svgpath=fig/} from the svg
 >package may also/additionally be needed.
 >

Excellent!  Adding to the top of my emacs .org file the following allowed it to work.  

#+LATEX_HEADER: \graphicspath{{fig/}}

Much better workaround.  But still a workaround?

~ Malcolm


 >Aaron
 >
 >PS Maybe org should be generating the \includesvg command relative to
 >the graphicspath or svgpath – I’m not sure.  But let us know if setting
 >those variables works at all, and if so we can think about adding
 >support to org.
 >
 >--
 >Aaron Ecay

  reply	other threads:[~2013-10-28 22:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  0:32 how to handle svg files when exporting orgmode to html and pdf? malcolm cook
2013-07-27  6:36 ` Aaron Ecay
2013-08-08 17:46   ` Malcolm Cook
2013-08-08 19:19     ` Nick Dokos
2013-08-08 21:15       ` Cook, Malcolm
2013-08-08 19:36     ` Aaron Ecay
2013-08-08 19:46       ` Malcolm Cook
2013-08-08 21:00         ` Aaron Ecay
2013-08-08 21:11           ` Malcolm Cook
2013-08-08 21:34             ` Aaron Ecay
2013-08-09  2:04               ` Malcolm Cook
2013-08-09 20:52                 ` Aaron Ecay
2013-08-09 21:01                 ` Cook, Malcolm
2013-10-28 19:18                   ` Cook, Malcolm
2013-10-28 20:02                     ` Aaron Ecay
2013-10-28 22:02                       ` Cook, Malcolm [this message]
2013-10-30  6:08                         ` Aaron Ecay
2013-08-09  4:43         ` Nick Dokos

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=D4772401B9D976478C0895769BE3E792C1A968@MBSRV02.sgc.loc \
    --to=mec@stowers.org \
    --cc=aaronecay@gmail.com \
    --cc=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    --cc=malcolm.cook@gmail.com \
    --cc=ndokos@gmail.com \
    --cc=philten@cern.ch \
    --cc=schulte.eric@gmail.com \
    --cc=tsd@tsdye.com \
    --cc=vbeffara@ens-lyon.fr \
    /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).