From: "Mark S." <throaway@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: Images not showing up in PDF output
Date: Sun, 6 Apr 2014 11:14:41 -0700 (PDT) [thread overview]
Message-ID: <1396808081.95189.YahooMailBasic@web141704.mail.bf1.yahoo.com> (raw)
In-Reply-To: <87ob0fk9lc.fsf@berkeley.edu>
Thanks Richard and Eric!
After running it in MikTex by itself, and doing some look-ups, I found that I needed:
1) To use unix style directories in the file paths
2) To use #+LATEX_HEADER: \usepackage[multidot]{grffile} in order to accommodate the extra dot
in the file name.
Thanks!
Mark
--------------------------------------------
On Sat, 4/5/14, Richard Lawrence <richard.lawrence@berkeley.edu> wrote:
Subject: Re: [O] Images not showing up in PDF output
To: emacs-orgmode@gnu.org
Cc: "Mark S." <throaway@yahoo.com>
Date: Saturday, April 5, 2014, 9:46 AM
Hi Mark,
> On Saturday, 5 Apr 2014 at 05:59, Mark S. wrote:
>> Hello,
>>
>> I was able to export a subtree as PDF, but the
images don't show
>> up. The images do export in HTML, and I can see
that there is LaTeX
>> code for it. It looks like this:
>>
>> \includegraphics[width=10em]{./Periodicals.org_20140402_202538_4928DjL.png}
>>
>> Are there settings or additional add-ons that I
need to produce the images?
In addition to Eric's advice, I would recommend that you
check that this
image is in the right directory, relative to where the .tex
file lives,
and relative to where LaTeX is being run. (Check the
compile log to see
if there are errors about not finding the image, or try to
compile the
exported .tex by hand, without the -interaction nonstopmode
option which
I believe is Org's default.)
I have sometimes run into problems (mostly with BibTeX) when
the
exported .tex file doesn't exist in the directory where
org-latex-pdf-process is run: even though the paths may look
right in
the .tex file, if the other files used in the compilation
(.aux, etc.)
don't end up in the right place, relative paths can break.
Best,
Richard
(If possible, please encrypt your reply to me using my PGP
key:
Key ID: CF6FA646
Fingerprint: 9969 43E1 CF6F A646.
See http://www.ocf.berkeley.edu/~rwl/encryption.html for
more information.)
prev parent reply other threads:[~2014-04-06 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 4:59 Images not showing up in PDF output Mark S.
2014-04-05 9:55 ` Eric S Fraga
2014-04-05 16:46 ` Richard Lawrence
2014-04-05 19:33 ` [OT] Don't use BibTeX! (was: Images not showing up in PDF output) Marcin Borkowski
2014-04-07 1:39 ` [OT] Don't use BibTeX! Richard Lawrence
2014-04-07 2:58 ` Thomas S. Dye
2014-04-07 3:50 ` Biblatex and Org [was: [OT] Don't use BibTeX!] Richard Lawrence
2014-04-07 8:34 ` Thomas S. Dye
2014-04-07 15:12 ` Biblatex and Org Richard Lawrence
2014-04-06 18:14 ` Mark S. [this message]
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=1396808081.95189.YahooMailBasic@web141704.mail.bf1.yahoo.com \
--to=throaway@yahoo.com \
--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).