Re: how to handle svg files when exporting orgmode to html and pdf?

[Malcolm Cook <malcolm.cook@gmail.com>]

Aaron,

Yeah, the zz was added by me whilst sleuthing.  Sorry for the
confusion.  I added it across the board though. Before I added it, the
message had been 'mtcars.zzpdf_tex' not found.'

I know with org I can directly :export :file basename.svg

The thing I am trying to accomplish is to find an approach that works
for both org export to html and org export to latex->pdf without
having to edit the org document in between exports.

When I do  :export :file basename.svg the resulting pdf does not
inline the svg.  Rather it contains a link to it.

I thought the dance with the svg package was a way of accomplishing my aim.

Do you see a better way?

Thanks!
--
Malcolm Cook
h - 913.642.5257
c - 913.226.1542
w - 816.926.4449


On Thu, Aug 8, 2013 at 4:00 PM, Aaron Ecay <aaronecay@gmail.com> wrote:
> Hi Malcom,
>
> It looks like there are two things going on.  The first is that you
> are (as Nick suspected) including the file twice in the document.  You
> should change the header of the babel block to output a SVG file:
>
> #+begin_src R :results  graphics output :exports both :file mtcars.svg
>                                                                    ^^^
>
> Then you don’t need the #+BEGIN/END_LATEX bit.
>
> The other bit is the svg package failing somehow.  Does the mtcars.svg
> file exist in the same directory?  (It isn’t being generated by the
> babel block, for example).  Is the inkscape binary you installed on your
> $PATH?  I am suspicious about this line from the log file:
>
> ,----
> | ! LaTeX Error: File `mtcars.zzpdf_tex' not found.
> `----
>
> The “zz” should not be there.  Could a stray “zz” have gotten into the
> svg.sty file?
>
> The svg package doesn’t have the greatest error reporting; if
> you keep having trouble it may be helpful to add \usepackage{trace} to
> the top of the document, and \traceon just before the \includesvg
> command, to try to see in more detail what steps it is trying (and
> possibly failing).  This will generate a voluminous log file...
>
> --
> Aaron Ecay