emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Timothée Flutre" <timflutre@gmail.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: naming image files before exporting to PDF
Date: Fri, 6 Feb 2015 10:15:10 +0100	[thread overview]
Message-ID: <CAGJVmuL4v4zXUp=DNPLg9Dbx9zUJjh=U1uXs+mCsQvhxZDPZ4Q@mail.gmail.com> (raw)
In-Reply-To: <m24mqzlb12.fsf@krugs.de>

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

Thanks for your answers. In fact, the problem comes from the LaTeX package
"underscore" (I had it in my ~/.emacs).

In this situation:

#+latex_header: \usepackage{underscore}
#+latex_header: \graphicspath{ {./images/} }
[[file:simul001_a-4_b-0-1.pdf]]
=> the image is not displayed

Whereas in this situation:
#+latex_header: \graphicspath{ {./images/} }
[[file:simul001_a-4_b-0-1.pdf]]
=> the image is displayed correctly

Therefore, if one needs to have any underscore in the text as well as in
image file names, the only way I found is to use the verbatim mode ("=" in
org-mode) to handle underscore in text.
Here is an example that works:

#+latex_header: \graphicspath{ {./images/} }
File name: =simul001_a-4_b-0-1.pdf=
[[file:simul001_a-4_b-0-1.pdf]]

Note also that underscore "_" and hyphen "-" work well separately as well
as together.

Timothée Flutre

2015-02-06 9:06 GMT+01:00 Rainer M Krug <Rainer@krugs.de>:

> 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: Type: text/html, Size: 2989 bytes --]

next prev parent reply	other threads:[~2015-02-06  9:15 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 [this message]
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='CAGJVmuL4v4zXUp=DNPLg9Dbx9zUJjh=U1uXs+mCsQvhxZDPZ4Q@mail.gmail.com' \
    --to=timflutre@gmail.com \
    --cc=Rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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

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).