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

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

[Malcolm Cook]

Hi,

I am creating .svg files with R source blocks and ESS in org.

I am happily viewing them in-line in my emacs buffer.

I am happily exporting as html and viewing them in-line in the resulting web page, including a table of images.

I do not have an approach for including them into PDF when I export->tex->pdf.

I'm thinking there might be an approach to converting them on-the-fly to png (or something) during the export->tex->pdf.

A similar problem was addressed with custom macros here: http://thread.gmane.org/gmane.emacs.orgmode/56532/focus=58322

But it does not work with  R source blocks that produce .svg files.

Any suggestions for me?  Is this a lost cause?  Am I asking for too many assumptions to be made by such an auto-conversion process that it is doomed to fail anyway?

Thanks for your thoughts and help!

Malcolm

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

[Suvayu Ali]

Hello Malcolm,

On Wed, Jul 17, 2013 at 05:25:15PM -0700, Malcolm Cook wrote:
> Hi,
> 
> I am creating .svg files with R source blocks and ESS in org.
> 
> I am happily viewing them in-line in my emacs buffer.
> 
> I am happily exporting as html and viewing them in-line in the resulting web page, including a table of images.
> 
> I do not have an approach for including them into PDF when I export->tex->pdf.
> 
> I'm thinking there might be an approach to converting them on-the-fly to png (or something) during the export->tex->pdf.
> 
> A similar problem was addressed with custom macros here: http://thread.gmane.org/gmane.emacs.orgmode/56532/focus=58322
> 
> But it does not work with  R source blocks that produce .svg files.
> 
> Any suggestions for me?  Is this a lost cause?  Am I asking for too many assumptions to be made by such an auto-conversion process that it is doomed to fail anyway?
> 

This kind of niche Org mode questions are more likely to be answered on
the Org mode list.  I would encourage you to post there in the future.

That said, maybe the following Worg entry will help you adapt it for R:
<http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html#sec-4-3>

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

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

[malcolm cook]

Hi, 

I am creating .svg files with R source blocks and ESS in org. 

I am happily viewing them in-line in my emacs buffer. 

I am happily exporting as html and viewing them in-line in the resulting web 
page, including a table of images. 

I do not have an approach for including them into PDF when I export-tex-pdf. 

I'm thinking there might be an approach to converting them on-the-fly to png 
(or something) during the export->tex->pdf. 

A similar problem was addressed with custom macros here: 
http://thread.gmane.org/gmane.emacs.orgmode/56532/focus=58322 

But it does not work with  R source blocks that produce .svg files. 

Any suggestions for me?  Is this a lost cause?  Am I asking for too many 
assumptions to be made by such an auto-conversion process that it is doomed 
to fail anyway? 

Thanks for your thoughts and help! 

Malcolm 

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

[Aaron Ecay]

Hi Malcom,

2013ko uztailak 17an, malcolm cook-ek idatzi zuen:
> 
> Hi, 
> 
> I am creating .svg files with R source blocks and ESS in org. 
> 
> I am happily viewing them in-line in my emacs buffer. 
> 
> I am happily exporting as html and viewing them in-line in the resulting web 
> page, including a table of images. 
> 
> I do not have an approach for including them into PDF when I export-tex-pdf. 
> 
> I'm thinking there might be an approach to converting them on-the-fly to png 
> (or something) during the export->tex->pdf. 
> 
> A similar problem was addressed with custom macros here: 
> http://thread.gmane.org/gmane.emacs.orgmode/56532/focus=58322 
> 
> But it does not work with  R source blocks that produce .svg files. 
> 
> Any suggestions for me?  Is this a lost cause?  Am I asking for too many 
> assumptions to be made by such an auto-conversion process that it is doomed 
> to fail anyway?

I have been using a variant of this workflow with some success.  Using a
patch I just pushed to the master branch, you should be able to
successfully export SVG image files to LaTeX documents, using the “svg”
LaTeX package: http://www.ctan.org/pkg/svg

No configuration should be needed on the org side.

The svg LaTeX package is a bit fussy.  It only works under pdfTeX (it
can be patched to work with LuaTeX, but cannot work with XeTeX at all).
It also requires you to have the inkscape command line program
installed.  But within those constraints it works very nicely.

You may need to arrange for whatever compilation process you use for
LaTeX files to pass the “-shell-escape” command line option to pdftex.
This allows TeX code to execute command line programs, which is needed
to communicate with inkscape and convert the SVG into something LaTeX
can use.

I think in the long run it would be nice if Org could help you translate
the image types in your document into image types an exporter
understands (basically an expanded and generalized version of what is
already done with LaTeX snippets for non-LaTeX export).  But that is
a bigger project, I think.

-- 
Aaron Ecay

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

[Malcolm Cook]

Aaron & Nick,

Thanks for the help.  I think I'm almost there.

So far I did

 * install a latex package (first time for everything).  I wound up
just putting svg.sty file it for now in the same directory as the .org
file since my attempts to date failed using $HOME/texfm
 * customize the emacs variable `org-latex-pdf-process` to include
'--shell-escape' (following advice in
http://orgmode.org/worg/org-dependencies.html, which outlines some
other options)
 * upgrade to inkscape version 0.48.+ (which is more recent than our
centOS repos proffered, but, hey) since the --export-latex switch that
svg.sty depends upon is not implemented till this version

When I "export to latex as PDF file", I get error "PDF file ./test.pdf
wasn't produced"

Sleuthing, I see the output .tex file includes the following lines:

\usepackage{svg}
...
\includegraphics[width=.9\linewidth]{mtcars.png}
@@backend:\includesvg{mtcars}

However, when they get processed, and the includesvg seeks the pdf_tex
file, I get this error:

! LaTeX Error: File `mtcars.pdf_tex' not found.
Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: pdf_tex)
Enter file name:
! Emergency stop.
<read *>
l.354 \includesvg{mtcars}

If you have any suggestions to me for further sleuthing I would be much obliged.

Thanks,

Malcolm Cook


On Sat, Jul 27, 2013 at 1:36 AM, Aaron Ecay <aaronecay@gmail.com> wrote:
>
> Hi Malcom,
>
> 2013ko uztailak 17an, malcolm cook-ek idatzi zuen:
> >
> > Hi,
> >
> > I am creating .svg files with R source blocks and ESS in org.
> >
> > I am happily viewing them in-line in my emacs buffer.
> >
> > I am happily exporting as html and viewing them in-line in the resulting web
> > page, including a table of images.
> >
> > I do not have an approach for including them into PDF when I export-tex-pdf.
> >
> > I'm thinking there might be an approach to converting them on-the-fly to png
> > (or something) during the export->tex->pdf.
> >
> > A similar problem was addressed with custom macros here:
> > http://thread.gmane.org/gmane.emacs.orgmode/56532/focus=58322
> >
> > But it does not work with  R source blocks that produce .svg files.
> >
> > Any suggestions for me?  Is this a lost cause?  Am I asking for too many
> > assumptions to be made by such an auto-conversion process that it is doomed
> > to fail anyway?
>
> I have been using a variant of this workflow with some success.  Using a
> patch I just pushed to the master branch, you should be able to
> successfully export SVG image files to LaTeX documents, using the “svg”
> LaTeX package: http://www.ctan.org/pkg/svg
>
> No configuration should be needed on the org side.
>
> The svg LaTeX package is a bit fussy.  It only works under pdfTeX (it
> can be patched to work with LuaTeX, but cannot work with XeTeX at all).
> It also requires you to have the inkscape command line program
> installed.  But within those constraints it works very nicely.
>
> You may need to arrange for whatever compilation process you use for
> LaTeX files to pass the “-shell-escape” command line option to pdftex.
> This allows TeX code to execute command line programs, which is needed
> to communicate with inkscape and convert the SVG into something LaTeX
> can use.
>
> I think in the long run it would be nice if Org could help you translate
> the image types in your document into image types an exporter
> understands (basically an expanded and generalized version of what is
> already done with LaTeX snippets for non-LaTeX export).  But that is
> a bigger project, I think.
>
> --
> Aaron Ecay

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

[Nick Dokos]

Malcolm Cook <malcolm.cook@gmail.com> writes:


> When I "export to latex as PDF file", I get error "PDF file ./test.pdf
> wasn't produced"
>

In case of difficulties like this, I produce the tex file (C-c C-e l l)
and then I process it by hand:

 pdflatex --shell-escape foo.tex

Separates concerns nicely.

> Sleuthing, I see the output .tex file includes the following lines:
>
> \usepackage{svg}
> ...
> \includegraphics[width=.9\linewidth]{mtcars.png}
> @@backend:\includesvg{mtcars}
>

This looks wrong. You probably want @@latex:\includesvg{mtcars}@@ in
your org file. In any case, the output in the tex file should be just

  \includesvg{mtcars}

Also, not sure how the \includegraphics is produced (are you evaluating a
source block?) but it should probably not be there, otherwise you are
going to get two images in your PDF.

-- 
Nick

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

[Cook, Malcolm]

>In case of difficulties like this, I produce the tex file (C-c C-e l l)
 >and then I process it by hand:
 >
 > pdflatex --shell-escape foo.tex
 >
 >Separates concerns nicely.

I will try your approach - thanks - I agree

 >
 >> Sleuthing, I see the output .tex file includes the following lines:
 >>
 >> \usepackage{svg}
 >> ...
 >> \includegraphics[width=.9\linewidth]{mtcars.png}
 >> @@backend:\includesvg{mtcars}
 >>
 >
 >This looks wrong. You probably want @@latex:\includesvg{mtcars}@@ in
 >your org file. In any case, the output in the tex file should be just
 >
 >  \includesvg{mtcars}
 >
 >Also, not sure how the \includegraphics is produced (are you evaluating a
 >source block?) 

Yes

> but it should probably not be there, otherwise you are
 >going to get two images in your PDF.

I was going to conditionally suppress it depending on value of ox-backend.....

If I can get this whole gamish to work for me at all....

~Malcolm

 >
 >--
 >Nick
 >

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

[Aaron Ecay]

Hi Malcom,

2013ko abuztuak 8an, Malcolm Cook-ek idatzi zuen:
> 
> Aaron & Nick,
> 
> Thanks for the help.  I think I'm almost there.
> 
> So far I did
> 
>  * install a latex package (first time for everything).  I wound up
> just putting svg.sty file it for now in the same directory as the .org
> file since my attempts to date failed using $HOME/texfm
>  * customize the emacs variable `org-latex-pdf-process` to include
> '--shell-escape' (following advice in
> http://orgmode.org/worg/org-dependencies.html, which outlines some
> other options)
>  * upgrade to inkscape version 0.48.+ (which is more recent than our
> centOS repos proffered, but, hey) since the --export-latex switch that
> svg.sty depends upon is not implemented till this version
> 
> When I "export to latex as PDF file", I get error "PDF file ./test.pdf
> wasn't produced"
> 
> Sleuthing, I see the output .tex file includes the following lines:
> 
> \usepackage{svg}
> ...
> \includegraphics[width=.9\linewidth]{mtcars.png}
> @@backend:\includesvg{mtcars}
  ^^^^^^^^^

This looks like (malformed?) org markup that has “escaped” into the
exported .tex file.  Are you still using some of the custom macros from
other threads?  Can you send a minimal example of the file that you are
trying to export, and the resulting exported .tex file?  The .log file
produced by LaTeX when compiling the .tex file may be helpful as well.

Thanks,

-- 
Aaron Ecay

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

[Malcolm Cook]

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

Aaron, thanks so much, I've attached all three....
--
Malcolm Cook
h - 913.642.5257
c - 913.226.1542
w - 816.926.4449


On Thu, Aug 8, 2013 at 2:36 PM, Aaron Ecay <aaronecay@gmail.com> wrote:
> Hi Malcom,
>
> 2013ko abuztuak 8an, Malcolm Cook-ek idatzi zuen:
>>
>> Aaron & Nick,
>>
>> Thanks for the help.  I think I'm almost there.
>>
>> So far I did
>>
>>  * install a latex package (first time for everything).  I wound up
>> just putting svg.sty file it for now in the same directory as the .org
>> file since my attempts to date failed using $HOME/texfm
>>  * customize the emacs variable `org-latex-pdf-process` to include
>> '--shell-escape' (following advice in
>> http://orgmode.org/worg/org-dependencies.html, which outlines some
>> other options)
>>  * upgrade to inkscape version 0.48.+ (which is more recent than our
>> centOS repos proffered, but, hey) since the --export-latex switch that
>> svg.sty depends upon is not implemented till this version
>>
>> When I "export to latex as PDF file", I get error "PDF file ./test.pdf
>> wasn't produced"
>>
>> Sleuthing, I see the output .tex file includes the following lines:
>>
>> \usepackage{svg}
>> ...
>> \includegraphics[width=.9\linewidth]{mtcars.png}
>> @@backend:\includesvg{mtcars}
>   ^^^^^^^^^
>
> This looks like (malformed?) org markup that has “escaped” into the
> exported .tex file.  Are you still using some of the custom macros from
> other threads?  Can you send a minimal example of the file that you are
> trying to export, and the resulting exported .tex file?  The .log file
> produced by LaTeX when compiling the .tex file may be helpful as well.
>
> Thanks,
>
> --
> Aaron Ecay

[-- Attachment #2: testsvg.log --]
[-- Type: application/octet-stream, Size: 31532 bytes --]

This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=pdflatex 2012.4.5)  8 AUG 2013 14:43
entering extended mode
\write18 enabled.
 %&-line parsing enabled.
**/home/mec/.emacs.d/testsvg.tex
(/home/mec/.emacs.d/testsvg.tex
LaTeX2e <2005/12/01>
Babel <v3.8h> and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, arabic, basque, bulgarian, coptic, welsh, czech, slovak, german, ng
erman, danish, esperanto, spanish, catalan, galician, estonian, farsi, finnish,
 french, greek, monogreek, ancientgreek, croatian, hungarian, interlingua, ibyc
us, indonesian, icelandic, italian, latin, mongolian, dutch, norsk, polish, por
tuguese, pinyin, romanian, russian, slovenian, uppersorbian, serbian, swedish, 
turkish, ukenglish, ukrainian, loaded.
(/usr/share/texmf/tex/latex/base/article.cls
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
(/usr/share/texmf/tex/latex/base/size11.clo
File: size11.clo 2005/09/16 v1.4f Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
)
(/usr/share/texmf/tex/latex/base/inputenc.sty
Package: inputenc 2006/05/05 v1.1b Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15

(/usr/share/texmf/tex/latex/base/utf8.def
File: utf8.def 2006/03/30 v1.1i UTF-8 support for inputenc
Now handling font encoding OML ...
... no UTF-8 mapping file for font encoding OML
Now handling font encoding T1 ...
... processing UTF-8 mapping file for font encodingT1

(/usr/share/texmf/tex/latex/base/t1enc.dfu
File: t1enc.dfu 2006/03/30 v1.1i UTF-8 support for inputenc
   defining Unicode char U+00A1 (decimal 161)
   defining Unicode char U+00A3 (decimal 163)
   defining Unicode char U+00AB (decimal 171)
   defining Unicode char U+00BB (decimal 187)
   defining Unicode char U+00BF (decimal 191)
   defining Unicode char U+00C0 (decimal 192)
   defining Unicode char U+00C1 (decimal 193)
   defining Unicode char U+00C2 (decimal 194)
   defining Unicode char U+00C3 (decimal 195)
   defining Unicode char U+00C4 (decimal 196)
   defining Unicode char U+00C5 (decimal 197)
   defining Unicode char U+00C6 (decimal 198)
   defining Unicode char U+00C7 (decimal 199)
   defining Unicode char U+00C8 (decimal 200)
   defining Unicode char U+00C9 (decimal 201)
   defining Unicode char U+00CA (decimal 202)
   defining Unicode char U+00CB (decimal 203)
   defining Unicode char U+00CC (decimal 204)
   defining Unicode char U+00CD (decimal 205)
   defining Unicode char U+00CE (decimal 206)
   defining Unicode char U+00CF (decimal 207)
   defining Unicode char U+00D0 (decimal 208)
   defining Unicode char U+00D1 (decimal 209)
   defining Unicode char U+00D2 (decimal 210)
   defining Unicode char U+00D3 (decimal 211)
   defining Unicode char U+00D4 (decimal 212)
   defining Unicode char U+00D5 (decimal 213)
   defining Unicode char U+00D6 (decimal 214)
   defining Unicode char U+00D8 (decimal 216)
   defining Unicode char U+00D9 (decimal 217)
   defining Unicode char U+00DA (decimal 218)
   defining Unicode char U+00DB (decimal 219)
   defining Unicode char U+00DC (decimal 220)
   defining Unicode char U+00DD (decimal 221)
   defining Unicode char U+00DE (decimal 222)
   defining Unicode char U+00DF (decimal 223)
   defining Unicode char U+00E0 (decimal 224)
   defining Unicode char U+00E1 (decimal 225)
   defining Unicode char U+00E2 (decimal 226)
   defining Unicode char U+00E3 (decimal 227)
   defining Unicode char U+00E4 (decimal 228)
   defining Unicode char U+00E5 (decimal 229)
   defining Unicode char U+00E6 (decimal 230)
   defining Unicode char U+00E7 (decimal 231)
   defining Unicode char U+00E8 (decimal 232)
   defining Unicode char U+00E9 (decimal 233)
   defining Unicode char U+00EA (decimal 234)
   defining Unicode char U+00EB (decimal 235)
   defining Unicode char U+00EC (decimal 236)
   defining Unicode char U+00ED (decimal 237)
   defining Unicode char U+00EE (decimal 238)
   defining Unicode char U+00EF (decimal 239)
   defining Unicode char U+00F0 (decimal 240)
   defining Unicode char U+00F1 (decimal 241)
   defining Unicode char U+00F2 (decimal 242)
   defining Unicode char U+00F3 (decimal 243)
   defining Unicode char U+00F4 (decimal 244)
   defining Unicode char U+00F5 (decimal 245)
   defining Unicode char U+00F6 (decimal 246)
   defining Unicode char U+00F8 (decimal 248)
   defining Unicode char U+00F9 (decimal 249)
   defining Unicode char U+00FA (decimal 250)
   defining Unicode char U+00FB (decimal 251)
   defining Unicode char U+00FC (decimal 252)
   defining Unicode char U+00FD (decimal 253)
   defining Unicode char U+00FE (decimal 254)
   defining Unicode char U+00FF (decimal 255)
   defining Unicode char U+0102 (decimal 258)
   defining Unicode char U+0103 (decimal 259)
   defining Unicode char U+0104 (decimal 260)
   defining Unicode char U+0105 (decimal 261)
   defining Unicode char U+0106 (decimal 262)
   defining Unicode char U+0107 (decimal 263)
   defining Unicode char U+010C (decimal 268)
   defining Unicode char U+010D (decimal 269)
   defining Unicode char U+010E (decimal 270)
   defining Unicode char U+010F (decimal 271)
   defining Unicode char U+0110 (decimal 272)
   defining Unicode char U+0111 (decimal 273)
   defining Unicode char U+0118 (decimal 280)
   defining Unicode char U+0119 (decimal 281)
   defining Unicode char U+011A (decimal 282)
   defining Unicode char U+011B (decimal 283)
   defining Unicode char U+011E (decimal 286)
   defining Unicode char U+011F (decimal 287)
   defining Unicode char U+0130 (decimal 304)
   defining Unicode char U+0131 (decimal 305)
   defining Unicode char U+0132 (decimal 306)
   defining Unicode char U+0133 (decimal 307)
   defining Unicode char U+0139 (decimal 313)
   defining Unicode char U+013A (decimal 314)
   defining Unicode char U+013D (decimal 317)
   defining Unicode char U+013E (decimal 318)
   defining Unicode char U+0141 (decimal 321)
   defining Unicode char U+0142 (decimal 322)
   defining Unicode char U+0143 (decimal 323)
   defining Unicode char U+0144 (decimal 324)
   defining Unicode char U+0147 (decimal 327)
   defining Unicode char U+0148 (decimal 328)
   defining Unicode char U+014A (decimal 330)
   defining Unicode char U+014B (decimal 331)
   defining Unicode char U+0150 (decimal 336)
   defining Unicode char U+0151 (decimal 337)
   defining Unicode char U+0152 (decimal 338)
   defining Unicode char U+0153 (decimal 339)
   defining Unicode char U+0154 (decimal 340)
   defining Unicode char U+0155 (decimal 341)
   defining Unicode char U+0158 (decimal 344)
   defining Unicode char U+0159 (decimal 345)
   defining Unicode char U+015A (decimal 346)
   defining Unicode char U+015B (decimal 347)
   defining Unicode char U+015E (decimal 350)
   defining Unicode char U+015F (decimal 351)
   defining Unicode char U+0160 (decimal 352)
   defining Unicode char U+0161 (decimal 353)
   defining Unicode char U+0162 (decimal 354)
   defining Unicode char U+0163 (decimal 355)
   defining Unicode char U+0164 (decimal 356)
   defining Unicode char U+0165 (decimal 357)
   defining Unicode char U+016E (decimal 366)
   defining Unicode char U+016F (decimal 367)
   defining Unicode char U+0170 (decimal 368)
   defining Unicode char U+0171 (decimal 369)
   defining Unicode char U+0178 (decimal 376)
   defining Unicode char U+0179 (decimal 377)
   defining Unicode char U+017A (decimal 378)
   defining Unicode char U+017B (decimal 379)
   defining Unicode char U+017C (decimal 380)
   defining Unicode char U+017D (decimal 381)
   defining Unicode char U+017E (decimal 382)
   defining Unicode char U+200C (decimal 8204)
   defining Unicode char U+2013 (decimal 8211)
   defining Unicode char U+2014 (decimal 8212)
   defining Unicode char U+2018 (decimal 8216)
   defining Unicode char U+2019 (decimal 8217)
   defining Unicode char U+201A (decimal 8218)
   defining Unicode char U+201C (decimal 8220)
   defining Unicode char U+201D (decimal 8221)
   defining Unicode char U+201E (decimal 8222)
   defining Unicode char U+2030 (decimal 8240)
   defining Unicode char U+2031 (decimal 8241)
   defining Unicode char U+2039 (decimal 8249)
   defining Unicode char U+203A (decimal 8250)
   defining Unicode char U+2423 (decimal 9251)
)
Now handling font encoding OT1 ...
... processing UTF-8 mapping file for font encodingOT1

(/usr/share/texmf/tex/latex/base/ot1enc.dfu
File: ot1enc.dfu 2006/03/30 v1.1i UTF-8 support for inputenc
   defining Unicode char U+00A1 (decimal 161)
   defining Unicode char U+00A3 (decimal 163)
   defining Unicode char U+00B8 (decimal 184)
   defining Unicode char U+00BF (decimal 191)
   defining Unicode char U+00C5 (decimal 197)
   defining Unicode char U+00C6 (decimal 198)
   defining Unicode char U+00D8 (decimal 216)
   defining Unicode char U+00DF (decimal 223)
   defining Unicode char U+00E6 (decimal 230)
   defining Unicode char U+00EC (decimal 236)
   defining Unicode char U+00ED (decimal 237)
   defining Unicode char U+00EE (decimal 238)
   defining Unicode char U+00EF (decimal 239)
   defining Unicode char U+00F8 (decimal 248)
   defining Unicode char U+0131 (decimal 305)
   defining Unicode char U+0141 (decimal 321)
   defining Unicode char U+0142 (decimal 322)
   defining Unicode char U+0152 (decimal 338)
   defining Unicode char U+0153 (decimal 339)
   defining Unicode char U+2013 (decimal 8211)
   defining Unicode char U+2014 (decimal 8212)
   defining Unicode char U+2018 (decimal 8216)
   defining Unicode char U+2019 (decimal 8217)
   defining Unicode char U+201C (decimal 8220)
   defining Unicode char U+201D (decimal 8221)
)
Now handling font encoding OMS ...
... processing UTF-8 mapping file for font encodingOMS

(/usr/share/texmf/tex/latex/base/omsenc.dfu
File: omsenc.dfu 2006/03/30 v1.1i UTF-8 support for inputenc
   defining Unicode char U+00A7 (decimal 167)
   defining Unicode char U+00B6 (decimal 182)
   defining Unicode char U+00B7 (decimal 183)
   defining Unicode char U+2020 (decimal 8224)
   defining Unicode char U+2021 (decimal 8225)
   defining Unicode char U+2022 (decimal 8226)
)
Now handling font encoding OMX ...
... no UTF-8 mapping file for font encoding OMX
Now handling font encoding U ...
... no UTF-8 mapping file for font encoding U
   defining Unicode char U+00A9 (decimal 169)
   defining Unicode char U+00AA (decimal 170)
   defining Unicode char U+00AE (decimal 174)
   defining Unicode char U+00BA (decimal 186)
   defining Unicode char U+02C6 (decimal 710)
   defining Unicode char U+02DC (decimal 732)
   defining Unicode char U+200C (decimal 8204)
   defining Unicode char U+2026 (decimal 8230)
   defining Unicode char U+2122 (decimal 8482)
   defining Unicode char U+2423 (decimal 9251)
))
(/usr/share/texmf/tex/latex/base/fontenc.sty
Package: fontenc 2005/09/27 v1.99g Standard LaTeX package

(/usr/share/texmf/tex/latex/base/t1enc.def
File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
LaTeX Font Info:    Redeclaring font encoding T1 on input line 43.
))
(/usr/share/texmf/tex/latex/base/fixltx2e.sty
Package: fixltx2e 2006/03/24 v1.1n fixes to LaTeX
LaTeX Info: Redefining \em on input line 420.
)
(/usr/share/texmf/tex/latex/graphics/graphicx.sty
Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR)

(/usr/share/texmf/tex/latex/graphics/keyval.sty
Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
\KV@toks@=\toks16
)
(/usr/share/texmf/tex/latex/graphics/graphics.sty
Package: graphics 2006/02/20 v1.0o Standard LaTeX Graphics (DPC,SPQR)

(/usr/share/texmf/tex/latex/graphics/trig.sty
Package: trig 1999/03/16 v1.09 sin cos tan (DPC)
)
(/usr/share/texmf/tex/latex/config/graphics.cfg
File: graphics.cfg 2007/01/18 v1.5 graphics configuration of teTeX/TeXLive
)
Package graphics Info: Driver file: pdftex.def on input line 90.

(/usr/share/texmf/tex/latex/pdftex-def/pdftex.def
File: pdftex.def 2007/01/08 v0.04d Graphics/color for pdfTeX
\Gread@gobject=\count87
))
\Gin@req@height=\dimen103
\Gin@req@width=\dimen104
)
(/usr/share/texmf/tex/latex/tools/longtable.sty
Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC)
\LTleft=\skip43
\LTright=\skip44
\LTpre=\skip45
\LTpost=\skip46
\LTchunksize=\count88
\LTcapwidth=\dimen105
\LT@head=\box26
\LT@firsthead=\box27
\LT@foot=\box28
\LT@lastfoot=\box29
\LT@cols=\count89
\LT@rows=\count90
\c@LT@tables=\count91
\c@LT@chunks=\count92
\LT@p@ftn=\toks17
)
(/usr/share/texmf/tex/latex/float/float.sty
Package: float 2001/11/08 v1.3d Float enhancements (AL)
\c@float@type=\count93
\float@exts=\toks18
\float@box=\box30
\@float@everytoks=\toks19
\@floatcapt=\box31
)
(/usr/share/texmf/tex/latex/wrapfig/wrapfig.sty
\wrapoverhang=\dimen106
\WF@size=\dimen107
\c@WF@wrappedlines=\count94
\WF@box=\box32
\WF@everypar=\toks20
Package: wrapfig 2003/01/31  v 3.6
)
(/usr/share/texmf/tex/latex/ltxmisc/ulem.sty
\UL@box=\box33
\UL@hyphenbox=\box34
\UL@skip=\skip47
\UL@hook=\toks21
\UL@pe=\count95
\UL@pixel=\dimen108
\ULC@box=\box35
Package: ulem 2000/05/26
\ULdepth=\dimen109
)
(/usr/share/texmf/tex/latex/base/textcomp.sty
Package: textcomp 2005/09/27 v1.99g Standard LaTeX package
Package textcomp Info: Sub-encoding information:
(textcomp)               5 = only ISO-Adobe without \textcurrency
(textcomp)               4 = 5 + \texteuro
(textcomp)               3 = 4 + \textohm
(textcomp)               2 = 3 + \textestimated + \textcurrency
(textcomp)               1 = TS1 - \textcircled - \t
(textcomp)               0 = TS1 (full)
(textcomp)             Font families with sub-encoding setting implement
(textcomp)             only a restricted character set as indicated.
(textcomp)             Family '?' is the default used for unknown fonts.
(textcomp)             See the documentation for details.
Package textcomp Info: Setting ? sub-encoding to TS1/1 on input line 71.

(/usr/share/texmf/tex/latex/base/ts1enc.def
File: ts1enc.def 2001/06/05 v3.0e (jk/car/fm) Standard LaTeX file
Now handling font encoding TS1 ...
... processing UTF-8 mapping file for font encoding TS1

(/usr/share/texmf/tex/latex/base/ts1enc.dfu
File: ts1enc.dfu 2006/03/30 v1.1i UTF-8 support for inputenc
   defining Unicode char U+00A2 (decimal 162)
   defining Unicode char U+00A3 (decimal 163)
   defining Unicode char U+00A4 (decimal 164)
   defining Unicode char U+00A5 (decimal 165)
   defining Unicode char U+00A6 (decimal 166)
   defining Unicode char U+00A7 (decimal 167)
   defining Unicode char U+00A8 (decimal 168)
   defining Unicode char U+00A9 (decimal 169)
   defining Unicode char U+00AA (decimal 170)
   defining Unicode char U+00AC (decimal 172)
   defining Unicode char U+00AE (decimal 174)
   defining Unicode char U+00AF (decimal 175)
   defining Unicode char U+00B0 (decimal 176)
   defining Unicode char U+00B1 (decimal 177)
   defining Unicode char U+00B2 (decimal 178)
   defining Unicode char U+00B3 (decimal 179)
   defining Unicode char U+00B4 (decimal 180)
   defining Unicode char U+00B5 (decimal 181)
   defining Unicode char U+00B6 (decimal 182)
   defining Unicode char U+00B7 (decimal 183)
   defining Unicode char U+00B9 (decimal 185)
   defining Unicode char U+00BA (decimal 186)
   defining Unicode char U+00BC (decimal 188)
   defining Unicode char U+00BD (decimal 189)
   defining Unicode char U+00BE (decimal 190)
   defining Unicode char U+00D7 (decimal 215)
   defining Unicode char U+00F7 (decimal 247)
   defining Unicode char U+0192 (decimal 402)
   defining Unicode char U+02C7 (decimal 711)
   defining Unicode char U+02D8 (decimal 728)
   defining Unicode char U+02DD (decimal 733)
   defining Unicode char U+0E3F (decimal 3647)
   defining Unicode char U+2016 (decimal 8214)
   defining Unicode char U+2020 (decimal 8224)
   defining Unicode char U+2021 (decimal 8225)
   defining Unicode char U+2022 (decimal 8226)
   defining Unicode char U+2030 (decimal 8240)
   defining Unicode char U+2031 (decimal 8241)
   defining Unicode char U+203B (decimal 8251)
   defining Unicode char U+203D (decimal 8253)
   defining Unicode char U+2044 (decimal 8260)
   defining Unicode char U+204E (decimal 8270)
   defining Unicode char U+2052 (decimal 8274)
   defining Unicode char U+20A1 (decimal 8353)
   defining Unicode char U+20A4 (decimal 8356)
   defining Unicode char U+20A6 (decimal 8358)
   defining Unicode char U+20A9 (decimal 8361)
   defining Unicode char U+20AB (decimal 8363)
   defining Unicode char U+20AC (decimal 8364)
   defining Unicode char U+20B1 (decimal 8369)
   defining Unicode char U+2103 (decimal 8451)
   defining Unicode char U+2116 (decimal 8470)
   defining Unicode char U+2117 (decimal 8471)
   defining Unicode char U+211E (decimal 8478)
   defining Unicode char U+2120 (decimal 8480)
   defining Unicode char U+2122 (decimal 8482)
   defining Unicode char U+2126 (decimal 8486)
   defining Unicode char U+2127 (decimal 8487)
   defining Unicode char U+212E (decimal 8494)
   defining Unicode char U+2190 (decimal 8592)
   defining Unicode char U+2191 (decimal 8593)
   defining Unicode char U+2192 (decimal 8594)
   defining Unicode char U+2193 (decimal 8595)
   defining Unicode char U+2329 (decimal 9001)
   defining Unicode char U+232A (decimal 9002)
   defining Unicode char U+2422 (decimal 9250)
   defining Unicode char U+25E6 (decimal 9702)
   defining Unicode char U+25EF (decimal 9711)
   defining Unicode char U+266A (decimal 9834)
))
LaTeX Info: Redefining \oldstylenums on input line 266.
Package textcomp Info: Setting cmr sub-encoding to TS1/0 on input line 281.
Package textcomp Info: Setting cmss sub-encoding to TS1/0 on input line 282.
Package textcomp Info: Setting cmtt sub-encoding to TS1/0 on input line 283.
Package textcomp Info: Setting cmvtt sub-encoding to TS1/0 on input line 284.
Package textcomp Info: Setting cmbr sub-encoding to TS1/0 on input line 285.
Package textcomp Info: Setting cmtl sub-encoding to TS1/0 on input line 286.
Package textcomp Info: Setting ccr sub-encoding to TS1/0 on input line 287.
Package textcomp Info: Setting ptm sub-encoding to TS1/4 on input line 288.
Package textcomp Info: Setting pcr sub-encoding to TS1/4 on input line 289.
Package textcomp Info: Setting phv sub-encoding to TS1/4 on input line 290.
Package textcomp Info: Setting ppl sub-encoding to TS1/3 on input line 291.
Package textcomp Info: Setting pag sub-encoding to TS1/4 on input line 292.
Package textcomp Info: Setting pbk sub-encoding to TS1/4 on input line 293.
Package textcomp Info: Setting pnc sub-encoding to TS1/4 on input line 294.
Package textcomp Info: Setting pzc sub-encoding to TS1/4 on input line 295.
Package textcomp Info: Setting bch sub-encoding to TS1/4 on input line 296.
Package textcomp Info: Setting put sub-encoding to TS1/5 on input line 297.
Package textcomp Info: Setting uag sub-encoding to TS1/5 on input line 298.
Package textcomp Info: Setting ugq sub-encoding to TS1/5 on input line 299.
Package textcomp Info: Setting ul8 sub-encoding to TS1/4 on input line 300.
Package textcomp Info: Setting ul9 sub-encoding to TS1/4 on input line 301.
Package textcomp Info: Setting augie sub-encoding to TS1/5 on input line 302.
Package textcomp Info: Setting dayrom sub-encoding to TS1/3 on input line 303.
Package textcomp Info: Setting dayroms sub-encoding to TS1/3 on input line 304.

Package textcomp Info: Setting pxr sub-encoding to TS1/0 on input line 305.
Package textcomp Info: Setting pxss sub-encoding to TS1/0 on input line 306.
Package textcomp Info: Setting pxtt sub-encoding to TS1/0 on input line 307.
Package textcomp Info: Setting txr sub-encoding to TS1/0 on input line 308.
Package textcomp Info: Setting txss sub-encoding to TS1/0 on input line 309.
Package textcomp Info: Setting txtt sub-encoding to TS1/0 on input line 310.
Package textcomp Info: Setting futs sub-encoding to TS1/4 on input line 311.
Package textcomp Info: Setting futx sub-encoding to TS1/4 on input line 312.
Package textcomp Info: Setting futj sub-encoding to TS1/4 on input line 313.
Package textcomp Info: Setting hlh sub-encoding to TS1/3 on input line 314.
Package textcomp Info: Setting hls sub-encoding to TS1/3 on input line 315.
Package textcomp Info: Setting hlst sub-encoding to TS1/3 on input line 316.
Package textcomp Info: Setting hlct sub-encoding to TS1/5 on input line 317.
Package textcomp Info: Setting hlx sub-encoding to TS1/5 on input line 318.
Package textcomp Info: Setting hlce sub-encoding to TS1/5 on input line 319.
Package textcomp Info: Setting hlcn sub-encoding to TS1/5 on input line 320.
Package textcomp Info: Setting hlcw sub-encoding to TS1/5 on input line 321.
Package textcomp Info: Setting hlcf sub-encoding to TS1/5 on input line 322.
Package textcomp Info: Setting pplx sub-encoding to TS1/3 on input line 323.
Package textcomp Info: Setting pplj sub-encoding to TS1/3 on input line 324.
Package textcomp Info: Setting ptmx sub-encoding to TS1/4 on input line 325.
Package textcomp Info: Setting ptmj sub-encoding to TS1/4 on input line 326.
)
(/usr/share/texmf/tex/latex/marvosym/marvosym.sty
Package: marvosym 2006/05/11 v2.1 Martin Vogel's Symbols font definitions
)
(/usr/share/texmf/tex/latex/wasysym/wasysym.sty
Package: wasysym 2003/10/30 v2.0 Wasy-2 symbol support package
\symwasy=\mathgroup4
LaTeX Font Info:    Overwriting symbol font `wasy' in version `bold'
(Font)                  U/wasy/m/n --> U/wasy/b/n on input line 90.
)
(/usr/share/texmf/tex/latex/base/latexsym.sty
Package: latexsym 1998/08/17 v2.2e Standard LaTeX package (lasy symbols)
\symlasy=\mathgroup5
LaTeX Font Info:    Overwriting symbol font `lasy' in version `bold'
(Font)                  U/lasy/m/n --> U/lasy/b/n on input line 47.
)
(/usr/share/texmf/tex/latex/amsfonts/amssymb.sty
Package: amssymb 2002/01/22 v2.2d

(/usr/share/texmf/tex/latex/amsfonts/amsfonts.sty
Package: amsfonts 2001/10/25 v2.2f
\@emptytoks=\toks22
\symAMSa=\mathgroup6
\symAMSb=\mathgroup7
LaTeX Font Info:    Overwriting math alphabet `\mathfrak' in version `bold'
(Font)                  U/euf/m/n --> U/euf/b/n on input line 132.
))
(/usr/share/texmf/tex/latex/amsmath/amstext.sty
Package: amstext 2000/06/29 v2.01

(/usr/share/texmf/tex/latex/amsmath/amsgen.sty
File: amsgen.sty 1999/11/30 v2.0
\@emptytoks=\toks23
\ex@=\dimen110
))
(/usr/share/texmf/tex/latex/hyperref/hyperref.sty
Package: hyperref 2007/02/07 v6.75r Hypertext links for LaTeX
\@linkdim=\dimen111
\Hy@linkcounter=\count96
\Hy@pagecounter=\count97

(/usr/share/texmf/tex/latex/hyperref/pd1enc.def
File: pd1enc.def 2007/02/07 v6.75r Hyperref: PDFDocEncoding definition (HO)
Now handling font encoding PD1 ...
... no UTF-8 mapping file for font encoding PD1
)
(/usr/share/texmf/tex/latex/config/hyperref.cfg
File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive
)
(/usr/share/texmf/tex/latex/oberdiek/kvoptions.sty
Package: kvoptions 2006/08/22 v2.4 Connects package keyval with LaTeX options (
HO)
)
Package hyperref Info: Hyper figures OFF on input line 2288.
Package hyperref Info: Link nesting OFF on input line 2293.
Package hyperref Info: Hyper index ON on input line 2296.
Package hyperref Info: Plain pages OFF on input line 2303.
Package hyperref Info: Backreferencing OFF on input line 2308.

Implicit mode ON; LaTeX internals redefined
Package hyperref Info: Bookmarks ON on input line 2444.
(/usr/share/texmf/tex/latex/ltxmisc/url.sty
\Urlmuskip=\muskip10
Package: url 2005/06/27  ver 3.2  Verb mode for urls, etc.
)
LaTeX Info: Redefining \url on input line 2599.
\Fld@menulength=\count98
\Field@Width=\dimen112
\Fld@charsize=\dimen113
\Choice@toks=\toks24
\Field@toks=\toks25
Package hyperref Info: Hyper figures OFF on input line 3102.
Package hyperref Info: Link nesting OFF on input line 3107.
Package hyperref Info: Hyper index ON on input line 3110.
Package hyperref Info: backreferencing OFF on input line 3117.
Package hyperref Info: Link coloring OFF on input line 3122.
\Hy@abspage=\count99
\c@Item=\count100
\c@Hfootnote=\count101
)
*hyperref using default driver hpdftex*
(/usr/share/texmf/tex/latex/hyperref/hpdftex.def
File: hpdftex.def 2007/02/07 v6.75r Hyperref driver for pdfTeX
\Fld@listcount=\count102
) (.//svg.sty
Package: svg 2012/09/05 v1.0 SVG inclusion and extraction

(/usr/share/texmf/tex/latex/xkeyval/xkeyval.sty
Package: xkeyval 2006/11/18 v2.5f package option processing (HA)

(/usr/share/texmf/tex/latex/xkeyval/xkeyval.tex
\XKV@toks=\toks26
\XKV@depth=\count103
File: xkeyval.tex 2006/11/18 v2.5f key=value parser (HA)
))
(/usr/share/texmf/tex/latex/subfig/subfig.sty
Package: subfig 2005/06/28 ver: 1.3 subfig package

(/usr/share/texmf/tex/latex/caption/caption.sty
Package: caption 2007/01/07 v3.0k Customising captions (AR)

(/usr/share/texmf/tex/latex/caption/caption3.sty
Package: caption3 2007/01/07 v3.0k caption3 kernel (AR)
\captionmargin=\dimen114
\captionmarginx=\dimen115
\captionwidth=\dimen116
\captionindent=\dimen117
\captionparindent=\dimen118
\captionhangindent=\dimen119
)
Package caption Info: float package v1.3 (or newer) detected on input line 275.

Package caption Info: hyperref package v6.74m (or newer) detected on input line
 304.
Package caption Info: longtable package v3.15 (or newer) detected on input line
 359.
)
\c@KVtest=\count104
\sf@farskip=\skip48
\sf@captopadj=\dimen120
\sf@capskip=\skip49
\sf@nearskip=\skip50
\c@subfigure=\count105
\c@subfigure@save=\count106
\c@lofdepth=\count107
\c@subtable=\count108
\c@subtable@save=\count109
\c@lotdepth=\count110
\sf@top=\skip51
\sf@bottom=\skip52
)
(/usr/share/texmf/tex/latex/ltxmisc/import.sty)
(/usr/share/texmf/tex/latex/oberdiek/transparent.sty
Package: transparent 2007/01/08 v1.0 Using a pdfTeX's color stack for transpare
ncy (HO)

(/usr/share/texmf/tex/generic/oberdiek/ifpdf.sty
Package: ifpdf 2006/02/20 v1.4 Provides the ifpdf switch (HO)
Package ifpdf Info: pdfTeX in pdf mode detected.
)
(/usr/share/texmf/tex/latex/oberdiek/auxhook.sty
Package: auxhook 2006/05/31 v1.0 Hooks for auxiliary files (HO)
))
(/usr/share/texmf/tex/latex/xcolor/xcolor.sty
Package: xcolor 2007/01/21 v2.11 LaTeX color extensions (UK)

(/usr/share/texmf/tex/latex/config/color.cfg
File: color.cfg 2007/01/18 v1.5 color configuration of teTeX/TeXLive
)
Package xcolor Info: Driver file: pdftex.def on input line 225.
Package xcolor Info: Model `cmy' substituted by `cmy0' on input line 1337.
Package xcolor Info: Model `hsb' substituted by `rgb' on input line 1341.
Package xcolor Info: Model `RGB' extended on input line 1353.
Package xcolor Info: Model `HTML' substituted by `rgb' on input line 1355.
Package xcolor Info: Model `Hsb' substituted by `hsb' on input line 1356.
Package xcolor Info: Model `tHsb' substituted by `hsb' on input line 1357.
Package xcolor Info: Model `HSB' substituted by `hsb' on input line 1358.
Package xcolor Info: Model `Gray' substituted by `gray' on input line 1359.
Package xcolor Info: Model `wave' substituted by `hsb' on input line 1360.
)
\SVG@out@width=\skip53
\SVG@out@height=\skip54
\c@svgfigure=\count111
) (.//testsvg.aux)
\openout1 = `testsvg.aux'.

LaTeX Font Info:    Checking defaults for OML/cmm/m/it on input line 27.
LaTeX Font Info:    ... okay on input line 27.
LaTeX Font Info:    Checking defaults for T1/cmr/m/n on input line 27.
LaTeX Font Info:    ... okay on input line 27.
LaTeX Font Info:    Checking defaults for OT1/cmr/m/n on input line 27.
LaTeX Font Info:    ... okay on input line 27.
LaTeX Font Info:    Checking defaults for OMS/cmsy/m/n on input line 27.
LaTeX Font Info:    ... okay on input line 27.
LaTeX Font Info:    Checking defaults for OMX/cmex/m/n on input line 27.
LaTeX Font Info:    ... okay on input line 27.
LaTeX Font Info:    Checking defaults for U/cmr/m/n on input line 27.
LaTeX Font Info:    ... okay on input line 27.
LaTeX Font Info:    Checking defaults for TS1/cmr/m/n on input line 27.
LaTeX Font Info:    Try loading font information for TS1+cmr on input line 27.

(/usr/share/texmf/tex/latex/base/ts1cmr.fd
File: ts1cmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info:    ... okay on input line 27.
LaTeX Font Info:    Checking defaults for PD1/pdf/m/n on input line 27.
LaTeX Font Info:    ... okay on input line 27.
Package hyperref Info: Link coloring OFF on input line 27.

(/usr/share/texmf/tex/latex/hyperref/nameref.sty
Package: nameref 2006/12/27 v2.28 Cross-referencing by name of section

(/usr/share/texmf/tex/latex/oberdiek/refcount.sty
Package: refcount 2006/02/20 v3.0 Data extraction from references (HO)
)
\c@section@level=\count112
)
LaTeX Info: Redefining \ref on input line 27.
LaTeX Info: Redefining \pageref on input line 27.
 (.//testsvg.out)
(.//testsvg.out)
\@outlinefile=\write3
\openout3 = `testsvg.out'.

 (/usr/share/texmf/tex/latex/ragged2e/ragged2e.sty
Package: ragged2e 2003/03/25 v2.04 ragged2e Package (MS)

(/usr/share/texmf/tex/latex/everysel/everysel.sty
Package: everysel 1999/06/08 v1.03 EverySelectfont Package (MS)
LaTeX Info: Redefining \selectfont on input line 125.
)
\CenteringLeftskip=\skip55
\RaggedLeftLeftskip=\skip56
\RaggedRightLeftskip=\skip57
\CenteringRightskip=\skip58
\RaggedLeftRightskip=\skip59
\RaggedRightRightskip=\skip60
\CenteringParfillskip=\skip61
\RaggedLeftParfillskip=\skip62
\RaggedRightParfillskip=\skip63
\JustifyingParfillskip=\skip64
\CenteringParindent=\skip65
\RaggedLeftParindent=\skip66
\RaggedRightParindent=\skip67
\JustifyingParindent=\skip68
)
Package caption Info: subref 1.2 or 1.3 detected on input line 27.
LaTeX Info: Redefining \subref on input line 27.
LaTeX Font Info:    Try loading font information for U+wasy on input line 30.

(/usr/share/texmf/tex/latex/wasysym/uwasy.fd
File: uwasy.fd 2003/10/30 v2.0 Wasy-2 symbol font definitions
)
LaTeX Font Info:    Try loading font information for U+lasy on input line 30.

(/usr/share/texmf/tex/latex/base/ulasy.fd
File: ulasy.fd 1998/08/17 v2.2e LaTeX symbol font definitions
)
LaTeX Font Info:    Try loading font information for U+msa on input line 30.

(/usr/share/texmf/tex/latex/amsfonts/umsa.fd
File: umsa.fd 2002/01/19 v2.2g AMS font definitions
)
LaTeX Font Info:    Try loading font information for U+msb on input line 30.

(/usr/share/texmf/tex/latex/amsfonts/umsb.fd
File: umsb.fd 2002/01/19 v2.2g AMS font definitions
) (.//testsvg.toc)
\tf@toc=\write4
\openout4 = `testsvg.toc'.

LaTeX Font Info:    Try loading font information for T1+cmtt on input line 32.

(/usr/share/texmf/tex/latex/base/t1cmtt.fd
File: t1cmtt.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
<mtcars.png, id=7, 481.8pt x 481.8pt>
File: mtcars.png Graphic file (type png)
 <use mtcars.png>
<./mtcars.png, id=8, 481.8pt x 481.8pt>
File: ./mtcars.png Graphic file (type png)
 <use ./mtcars.png>
File: ./mtcars.png Graphic file (type png)
 <use ./mtcars.png>

! LaTeX Error: File `mtcars.zzpdf_tex' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: zzpdf_tex)

Enter file name: 
! Emergency stop.
<read *> 
         
l.39 \includesvg{mtcars}
                        ^^M
*** (cannot \read from terminal in nonstop modes)

 
Here is how much of TeX's memory you used:
 5831 strings out of 256216
 77364 string characters out of 1917073
 137008 words of memory out of 1500000
 8982 multiletter control sequences out of 10000+200000
 13711 words of font info for 45 fonts, out of 1200000 for 2000
 645 hyphenation exceptions out of 8191
 67i,6n,95p,285b,205s stack positions out of 5000i,500n,6000p,200000b,15000s
!  ==> Fatal error occurred, no output PDF file produced!

[-- Attachment #3: testsvg.tex --]
[-- Type: application/x-tex, Size: 823 bytes --]

[-- Attachment #4: testsvg.org --]
[-- Type: application/octet-stream, Size: 241 bytes --]

#+begin_src R :results  graphics output :exports both :file mtcars.png 
library(ggplot2)
qplot(wt, mpg, data = mtcars)
#+end_src

#+RESULTS:
[[file:mtcars.png]]

#+LATEX_HEADER: \usepackage{svg}
#+BEGIN_LaTeX
\includesvg{mtcars}
#+END_LaTeX

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

[Aaron Ecay]

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

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

[Malcolm Cook]

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

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

[Aaron Ecay]

Hi Malcom,
        
There is a patch that was added to the master branch of the org git
repository on Jul 27, which turns this from a link into a real inclusion
of the image.  So, it will only work as intended if you are using a git
checkout from after that date.

My apologies, I should have made this more prominent in my earlier
mails.

-- 
Aaron Ecay

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

[Malcolm Cook]

Aaron,

Thanks for staying with me on this.

I'm not sure what you're suggesting.

Nonetheless, I just updated org from `git clone git://orgmode.org/org-mode.git`

So, now I'm got org-version  release_8.0.7-377-gef2d47.dirty.

Are you suggesting that  with this patch.svg created with exporting
graphics :file should now display in the emacs buffer when I toggle
display of inline images?  I wish they would.  They do not, despite my
adding "svg" to org-export-latex-inline-image-extensions.

Are you suggesting that such a .svg created by org code block would be
appear in the pdf created when I export to latex -> pdf?  I wish that
also... that's what I've been trying to accomplish.

Thanks!,


Malcolm


PS - I see you are/were in PA in linguistics.   My first job after my
masters in AI from U Mass was at CMU's psych dept as a lisp programmer
for John Anderson's intelligent tutoring systems.  I then went on in
computational linguistics a bit, working on a marcus parser based
natural language processing system at wang labs.  Ages ago.  Now I'm
in computational biology.  The one commonality through it all?  Emacs!
--
Malcolm Cook
h - 913.642.5257
c - 913.226.1542
w - 816.926.4449


On Thu, Aug 8, 2013 at 4:34 PM, Aaron Ecay <aaronecay@gmail.com> wrote:
> Hi Malcom,
>
> There is a patch that was added to the master branch of the org git
> repository on Jul 27, which turns this from a link into a real inclusion
> of the image.  So, it will only work as intended if you are using a git
> checkout from after that date.
>
> My apologies, I should have made this more prominent in my earlier
> mails.
>
> --
> Aaron Ecay

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

[Aaron Ecay]

[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]

Hi Malcom,

On Thu, Aug 8, 2013 at 10:04 PM, Malcolm Cook <malcolm.cook@gmail.com> wrote:
> Aaron,
>
> Thanks for staying with me on this.
>
> I'm not sure what you're suggesting.
>
> Nonetheless, I just updated org from `git clone git://orgmode.org/org-mode.git`
>
> So, now I'm got org-version  release_8.0.7-377-gef2d47.dirty.
>
> Are you suggesting that  with this patch.svg created with exporting
> graphics :file should now display in the emacs buffer when I toggle
> display of inline images?  I wish they would.  They do not, despite my
> adding "svg" to org-export-latex-inline-image-extensions.

This I believe relies on your emacs binary having support for svg
images.  You can check if emacs is linked against librsvg with the
following shell command (assuming you are on linux):
$ ldd `which emacs` | grep svg

Which should give you some line of output like
    librsvg-2.so.2 => /usr/lib/librsvg-2.so.2 (0xb6a86000)

Within emacs, M-: (image-type-available-p 'svg) RET should display t

In buffer viewing of svg works for me without any additional setup,
upon pressing C-c C-x C-v, in an emacs with svg support.

>
> Are you suggesting that such a .svg created by org code block would be
> appear in the pdf created when I export to latex -> pdf?  I wish that
> also... that's what I've been trying to accomplish.

Yes.  I'm attaching the testsvg.org file (slightly modified from the
one you sent) and resultant latex export I get from the same git
version as you...as you can see, the [[file:mtcars.svg]] link is
translated into an \includesvg LaTeX command.  Does it work the same
for you?

>
> PS - I see you are/were in PA in linguistics.   My first job after my
> masters in AI from U Mass was at CMU's psych dept as a lisp programmer
> for John Anderson's intelligent tutoring systems.  I then went on in
> computational linguistics a bit, working on a marcus parser based
> natural language processing system at wang labs.  Ages ago.  Now I'm
> in computational biology.  The one commonality through it all?  Emacs!

:)  I'm in the doctoral program in linguistics at Penn, and a happy
emacs user for several years.  Here's to many more!

[-- Attachment #2: testsvg.org --]
[-- Type: application/octet-stream, Size: 161 bytes --]

#+begin_src R :results  graphics output :exports both :file mtcars.svg
library(ggplot2)
qplot(wt, mpg, data = mtcars)
#+end_src

#+RESULTS:
[[file:mtcars.svg]]


[-- Attachment #3: testsvg.tex --]
[-- Type: application/x-tex, Size: 760 bytes --]

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

[Cook, Malcolm]

Thomas, Suvayu, Aaron, Nick, Eric, Carsten, Phil, et al,

Thanks for all your help.

I am now satisfied with approach for exporting images to inline html and inline latex=>pdf.

In my hands, the following code block will produce in-line images in html and be included in exported pdf.

#+LATEX_HEADER: \usepackage{svg}
#+begin_src R :results  graphics output :exports both :file mtcars.svg
with(mtcars,plot(wt, mpg))
#+end_src 

I am using:
	Emacs 24.3.1
	Suvayus orgmode export filter:

(defun my-svg-graphics (contents backend info)
  (when (eq backend 'latex)
  (replace-regexp-in-string "\\`\\\\includegraphics.+\\({.+\.svg}\\)"
       "\\\\includesvg\1" contents))
)
(add-to-list 'org-export-filter-link-functions 'my-svg-graphics)

* svg latex package v1.0 2004/11/05

 * customize the emacs variable `org-latex-pdf-process` to include
'--shell-escape' (following advice in
http://orgmode.org/worg/org-dependencies.html, which outlines some
other options)

* customize org-export-html-inline-image-extensions to include  "svg" 

 * upgrade to inkscape version 0.48.+ (which is more recent than our
centOS repos proffered, but, hey) since the --export-latex switch that
svg.sty depends upon is not implemented till this version

* upgrade org-mode version 8.0.7-377 built from git pull yesterday

I think I've covered all the pieces.

I have not explored how/whether any options passed to includegraphics are interpreted by includesvg.

Now, if I could get .svg images to display inline in my emacs buffer.  The following is not respected, at least in my hands.  
	'(org-export-latex-inline-image-extensions (quote ("pdf" "jpeg" "jpg" "png" "ps" "eps" "svg")))
Any takers?


~ Malcolm



 >-----Original Message-----
 >From: emacs-orgmode-bounces+mec=stowers.org@gnu.org [mailto:emacs-orgmode-bounces+mec=stowers.org@gnu.org] On
 >Behalf Of Malcolm Cook
 >Sent: Thursday, August 08, 2013 9:05 PM
 >To: Malcolm Cook; emacs-orgmode@gnu.org; Nick Dokos
 >Subject: Re: [O] how to handle svg files when exporting orgmode to html and pdf?
 >
 >Aaron,
 >
 >Thanks for staying with me on this.
 >
 >I'm not sure what you're suggesting.
 >
 >Nonetheless, I just updated org from `git clone git://orgmode.org/org-mode.git`
 >
 >So, now I'm got org-version  release_8.0.7-377-gef2d47.dirty.
 >
 >Are you suggesting that  with this patch.svg created with exporting
 >graphics :file should now display in the emacs buffer when I toggle
 >display of inline images?  I wish they would.  They do not, despite my
 >adding "svg" to org-export-latex-inline-image-extensions.
 >
 >Are you suggesting that such a .svg created by org code block would be
 >appear in the pdf created when I export to latex -> pdf?  I wish that
 >also... that's what I've been trying to accomplish.
 >
 >Thanks!,
 >
 >
 >Malcolm
 >
 >
 >PS - I see you are/were in PA in linguistics.   My first job after my
 >masters in AI from U Mass was at CMU's psych dept as a lisp programmer
 >for John Anderson's intelligent tutoring systems.  I then went on in
 >computational linguistics a bit, working on a marcus parser based
 >natural language processing system at wang labs.  Ages ago.  Now I'm
 >in computational biology.  The one commonality through it all?  Emacs!
 >--
 >Malcolm Cook
 >h - 913.642.5257
 >c - 913.226.1542
 >w - 816.926.4449
 >
 >
 >On Thu, Aug 8, 2013 at 4:34 PM, Aaron Ecay <aaronecay@gmail.com> wrote:
 >> Hi Malcom,
 >>
 >> There is a patch that was added to the master branch of the org git
 >> repository on Jul 27, which turns this from a link into a real inclusion
 >> of the image.  So, it will only work as intended if you are using a git
 >> checkout from after that date.
 >>
 >> My apologies, I should have made this more prominent in my earlier
 >> mails.
 >>
 >> --
 >> Aaron Ecay

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

[Cook, Malcolm]

Thomas, Suvayu, Aaron, Nick, Eric, Carsten, Phil, et al,

Hi again!

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

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.

The workaround for (1) is to not use '%' as a label on my plots.

The workaround for (2) is to not put my figures in a './fig/' subdirectory.

I suppose the fix for (1) is to get the inkscape export 'fixed' to (optionally) escape the labels, and to take the option.  Thoughts?

I suppose the fix for (2) is somewhere in the org code.  Any takers?

Or, any other fixes suggested?

Thanks!

Malcolm



 >-----Original Message-----
 >From: emacs-orgmode-bounces+mec=stowers.org@gnu.org [mailto:emacs-orgmode-bounces+mec=stowers.org@gnu.org] On
 >Behalf Of Cook, Malcolm
 >Sent: Friday, August 09, 2013 4:01 PM
 >To: 'Malcolm Cook'; 'emacs-orgmode@gnu.org'; 'Nick Dokos'; 'Suvayu Ali'; 'Eric Schulte'; 'Vincent Beffara'; 'Thomas S. Dye';
 >'philten@cern.ch'; 'Charles Berry'; 'Aaron Ecay'
 >Subject: Re: [O] how to handle svg files when exporting orgmode to html and pdf?
 >
 >Thomas, Suvayu, Aaron, Nick, Eric, Carsten, Phil, et al,
 >
 >Thanks for all your help.
 >
 >I am now satisfied with approach for exporting images to inline html and inline latex=>pdf.
 >
 >In my hands, the following code block will produce in-line images in html and be included in exported pdf.
 >
 >#+LATEX_HEADER: \usepackage{svg}
 >#+begin_src R :results  graphics output :exports both :file mtcars.svg
 >with(mtcars,plot(wt, mpg))
 >#+end_src
 >
 >I am using:
 >	Emacs 24.3.1
 >	Suvayus orgmode export filter:
 >
 >(defun my-svg-graphics (contents backend info)
 >  (when (eq backend 'latex)
 >  (replace-regexp-in-string "\\`\\\\includegraphics.+\\({.+\.svg}\\)"
 >       "\\\\includesvg\1" contents))
 >)
 >(add-to-list 'org-export-filter-link-functions 'my-svg-graphics)
 >
 >* svg latex package v1.0 2004/11/05
 >
 > * customize the emacs variable `org-latex-pdf-process` to include
 >'--shell-escape' (following advice in
 >http://orgmode.org/worg/org-dependencies.html, which outlines some
 >other options)
 >
 >* customize org-export-html-inline-image-extensions to include  "svg"
 >
 > * upgrade to inkscape version 0.48.+ (which is more recent than our
 >centOS repos proffered, but, hey) since the --export-latex switch that
 >svg.sty depends upon is not implemented till this version
 >
 >* upgrade org-mode version 8.0.7-377 built from git pull yesterday
 >
 >I think I've covered all the pieces.
 >
 >I have not explored how/whether any options passed to includegraphics are interpreted by includesvg.
 >
 >Now, if I could get .svg images to display inline in my emacs buffer.  The following is not respected, at least in my hands.
 >	'(org-export-latex-inline-image-extensions (quote ("pdf" "jpeg" "jpg" "png" "ps" "eps" "svg")))
 >Any takers?
 >
 >
 >~ Malcolm
 >
 >
 >
 > >-----Original Message-----
 > >From: emacs-orgmode-bounces+mec=stowers.org@gnu.org [mailto:emacs-orgmode-bounces+mec=stowers.org@gnu.org] On
 > >Behalf Of Malcolm Cook
 > >Sent: Thursday, August 08, 2013 9:05 PM
 > >To: Malcolm Cook; emacs-orgmode@gnu.org; Nick Dokos
 > >Subject: Re: [O] how to handle svg files when exporting orgmode to html and pdf?
 > >
 > >Aaron,
 > >
 > >Thanks for staying with me on this.
 > >
 > >I'm not sure what you're suggesting.
 > >
 > >Nonetheless, I just updated org from `git clone git://orgmode.org/org-mode.git`
 > >
 > >So, now I'm got org-version  release_8.0.7-377-gef2d47.dirty.
 > >
 > >Are you suggesting that  with this patch.svg created with exporting
 > >graphics :file should now display in the emacs buffer when I toggle
 > >display of inline images?  I wish they would.  They do not, despite my
 > >adding "svg" to org-export-latex-inline-image-extensions.
 > >
 > >Are you suggesting that such a .svg created by org code block would be
 > >appear in the pdf created when I export to latex -> pdf?  I wish that
 > >also... that's what I've been trying to accomplish.
 > >
 > >Thanks!,
 > >
 > >
 > >Malcolm
 > >
 > >
 > >PS - I see you are/were in PA in linguistics.   My first job after my
 > >masters in AI from U Mass was at CMU's psych dept as a lisp programmer
 > >for John Anderson's intelligent tutoring systems.  I then went on in
 > >computational linguistics a bit, working on a marcus parser based
 > >natural language processing system at wang labs.  Ages ago.  Now I'm
 > >in computational biology.  The one commonality through it all?  Emacs!
 > >--
 > >Malcolm Cook
 > >h - 913.642.5257
 > >c - 913.226.1542
 > >w - 816.926.4449
 > >
 > >
 > >On Thu, Aug 8, 2013 at 4:34 PM, Aaron Ecay <aaronecay@gmail.com> wrote:
 > >> Hi Malcom,
 > >>
 > >> There is a patch that was added to the master branch of the org git
 > >> repository on Jul 27, which turns this from a link into a real inclusion
 > >> of the image.  So, it will only work as intended if you are using a git
 > >> checkout from after that date.
 > >>
 > >> My apologies, I should have made this more prominent in my earlier
 > >> mails.
 > >>
 > >> --
 > >> Aaron Ecay
 >

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

[Aaron Ecay]

Hi Malcom,

2013ko urriak 28an, "Cook, Malcolm"-ek idatzi zuen:
> 
> Thomas, Suvayu, Aaron, Nick, Eric, Carsten, Phil, et al,
> 
> Hi again!
> 
> 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.

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.

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

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

[Cook, Malcolm]

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

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

[Aaron Ecay]

Hi Malcom,

2013ko urriak 28an, "Cook, Malcolm"-ek idatzi zuen:
> 

[...]

> 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?

The support for including graphics from other directories in latex
documents doesn’t strike me as robust, and I think the \graphicspath
specification is often needed in such cases.  (Though I’m far from an
expert).  So I think it is indeed a workaround, but of the usual LaTeX
sort.

-- 
Aaron Ecay

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

[Nick Dokos]

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

Malcolm Cook <malcolm.cook@gmail.com> writes:

>
> #+begin_src R :results  graphics output :exports both :file mtcars.png 
> library(ggplot2)
> qplot(wt, mpg, data = mtcars)
> #+end_src
>
> #+RESULTS:
> [[file:mtcars.png]]
>
> #+LATEX_HEADER: \usepackage{svg}
> #+BEGIN_LaTeX
> \includesvg{mtcars}
> #+END_LaTeX


The following works for me:

--8<---------------cut here---------------start------------->8---
#+LATEX_HEADER: \usepackage{svg}

#+begin_src R :results  graphics output :exports both :file mtcars.svg :results none
library(ggplot2)
qplot(wt, mpg, data = mtcars)
#+end_src

#+BEGIN_LaTeX
\includesvg{mtcars}
#+END_LaTeX
--8<---------------cut here---------------end--------------->8---

The only problem is that I use minted to typeset code blocks and it
apparently does not know how to deal with R code blocks, so the code
block is not present in the PDF file. But the image is there. I attach
the resultant tex and pdf files.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: TeX file --]
[-- Type: text/x-tex, Size: 794 bytes --]

% Created 2013-08-09 Fri 00:36
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage[normalem]{ulem}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{amstext}
\usepackage{hyperref}
\tolerance=1000
\usepackage{minted}
\usepackage{svg}
\author{Nick Dokos}
\date{\today}
\title{foo2}
\hypersetup{
  pdfkeywords={},
  pdfsubject={},
  pdfcreator={Emacs 24.3.50.2 (Org mode 8.0.7)}}
\begin{document}

\maketitle
\tableofcontents

\begin{minted}[]{R}
library(ggplot2)
qplot(wt, mpg, data = mtcars)
\end{minted}

\includesvg{mtcars}
% Emacs 24.3.50.2 (Org mode 8.0.7)
\end{document}

[-- Attachment #3: PDF file --]
[-- Type: application/pdf, Size: 49502 bytes --]

[-- Attachment #4: Type: text/plain, Size: 10 bytes --]


-- 
Nick