From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: naming image files before exporting to PDF
Date: Fri, 06 Feb 2015 09:21:35 +0000 [thread overview]
Message-ID: <olu386jwg2o.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: m24mqzlb12.fsf@krugs.de
Hi,
usually, the grffile package works very well.
Try this, which works fine for me:
--8<---------------cut here---------------start------------->8---
#+latex_header: \graphicspath{ {./images/} }
#+latex_header: \usepackage{grffile}
* test
In the org file, it would look like this:
[[file:simul001_a-4_b-0.1.pdf]]
--8<---------------cut here---------------end--------------->8---
Best,
Andreas
Rainer M Krug <Rainer@krugs.de> writes:
> I remember a similar problem, and the cuprit was the dot. If I remember
> correctly, LaTeX was interpreting everything after the *first* "." as
> the extension.
>
> After avoiding "." in file names for images, it worked.
>
> "_" are fine.
>
> Rainer
>
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> Dashes are usually fine. Did you try replacing the _ with -?
>>
>> I try to avoid _ in filenames, but - works for me.
>>
>> On Thu, Feb 5, 2015 at 6:42 PM, Timothée Flutre <timflutre@gmail.com> wrote:
>>
>>> In the org file, it would look like this:
>>> #+latex_header: \graphicspath{ {./images/} }
>>> [[file:simul001_a-4_b-0.1.pdf]]
>>
>>
>>
>>
>> John
>>
>> -----------------------------------
>> Professor John Kitchin
>> Doherty Hall A207F
>> Department of Chemical Engineering
>> Carnegie Mellon University
>> Pittsburgh, PA 15213
>> 412-268-7803
>> @johnkitchin
>> http://kitchingroup.cheme.cmu.edu
prev parent reply other threads:[~2015-02-06 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 23:42 naming image files before exporting to PDF Timothée Flutre
2015-02-06 0:18 ` John Kitchin
2015-02-06 8:06 ` Rainer M Krug
2015-02-06 9:15 ` Timothée Flutre
2015-02-06 9:21 ` Andreas Leha [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=olu386jwg2o.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).