From: Rainer M Krug <Rainer@krugs.de>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>, timflutre@gmail.com
Subject: Re: naming image files before exporting to PDF
Date: Fri, 06 Feb 2015 09:06:01 +0100 [thread overview]
Message-ID: <m24mqzlb12.fsf@krugs.de> (raw)
In-Reply-To: <CAJ51ETo2kX6r=6v7FRKjigjBsP3C_dKZUDR8CK0v9AsbcSoyeA@mail.gmail.com> (John Kitchin's message of "Thu, 5 Feb 2015 19:18:58 -0500")
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
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
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2015-02-06 8:06 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 [this message]
2015-02-06 9:15 ` Timothée Flutre
2015-02-06 9:21 ` Andreas Leha
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=m24mqzlb12.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=timflutre@gmail.com \
/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).