You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting this weird behavior when rendering my bookdown project into a PDF file. And I'm almos sure it has a quick fix, but I was not able to find any through my searches.
While my bookdownproj.Rmd file properly shows image paths, the TEX file generated from it lacks the extension on the paths for images, thus failing to compile.
For instance,
Error: LaTeX failed to compile bookdownproj.tex.
In parse_packages(...) :
Failed to find a package that contains figs/figure1
Where 'figs/figure1' above should present the path to the file, such as as 'figs/figure1.svg' or 'figs/figure1.jpg'.
It is worth noting that many them are SVG images or link to images on the internet. Do I have to generate PNG or JPG images from SVG ones or place them locally (download) prior redering the PDF file?
Thanks in advance
Thiago
The text was updated successfully, but these errors were encountered:
depaulats
changed the title
LaTeX failed to compile TEX file. Path to SVG images have no file extensions.
LaTeX failed to compile TEX file. Path to images have no file extensions.
Mar 12, 2023
Hey guys,
I'm getting this weird behavior when rendering my bookdown project into a PDF file. And I'm almos sure it has a quick fix, but I was not able to find any through my searches.
While my bookdownproj.Rmd file properly shows image paths, the TEX file generated from it lacks the extension on the paths for images, thus failing to compile.
For instance,
Where 'figs/figure1' above should present the path to the file, such as as 'figs/figure1.svg' or 'figs/figure1.jpg'.
It is worth noting that many them are SVG images or link to images on the internet. Do I have to generate PNG or JPG images from SVG ones or place them locally (download) prior redering the PDF file?
Thanks in advance
Thiago
The text was updated successfully, but these errors were encountered: