From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Timoth=C3=A9e_Flutre?= Subject: naming image files before exporting to PDF Date: Fri, 6 Feb 2015 00:42:44 +0100 Message-ID: Reply-To: timflutre@gmail.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7bb0498e7f0bf1050e5fdd3e Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35122) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJW4i-0004Zo-AT for emacs-orgmode@gnu.org; Thu, 05 Feb 2015 18:43:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YJW4f-00015s-VU for emacs-orgmode@gnu.org; Thu, 05 Feb 2015 18:43:08 -0500 Received: from mail-wg0-x232.google.com ([2a00:1450:400c:c00::232]:42917) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJW4f-00015b-OE for emacs-orgmode@gnu.org; Thu, 05 Feb 2015 18:43:05 -0500 Received: by mail-wg0-f50.google.com with SMTP id b13so10381637wgh.9 for ; Thu, 05 Feb 2015 15:43:04 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --047d7bb0498e7f0bf1050e5fdd3e Content-Type: text/plain; charset=UTF-8 Hello, I am using Emacs 24.3.1 + Org-mode 8.2.10 for my work and would like to include images (typically output files in PDF from R) in my org files. Such image files correspond to graphics describing computer simulations. Thus, I would like to name them as meaningfully as possible, for instance simul001_a-4_b-0.1.pdf, which would indicate that parameter a was fixed at 4 and parameter b at 0.1 for the first simulation. In the org file, it would look like this: #+latex_header: \graphicspath{ {./images/} } [[file:simul001_a-4_b-0.1.pdf]] After doing C-c C-e l l, the tex file would look like that: ... \includegraphics[width=.9\linewidth]{simul001_a-4_b-0.1.pdf} ... However, after C-c C-e l p, it doesn't work. Instead of the image, the pdf contains the following sentence, _a-4_b-0.1.pdf _a-4_b-0.1.pdf. I tested with "simul001.pdf", and it works smoothly. I tested with "simul001_a_4_b_0_1.pdf", and it doesn't work. Instead of the image, the pdf contains the following sentence, _a_4_b_0_1.pdf _a_4_b_0_1.pdf, followed by an empty box containg somethign like simul001\unhbox \voidb@x \penalty \@M \hskip \z@skip. I know that LaTeX doesn't like special characters in file names to include. However, I thought that underscores and hyphens were ok. As I guess I'm not the only one who wants to name his files meaningfully, I wonder how other people do. Would anyone have any idea? TF --047d7bb0498e7f0bf1050e5fdd3e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I am using Em= acs 24.3.1 + Org-mode 8.2.10 for my work and would like to include images (= typically output files in PDF from R) in my org files. Such image files cor= respond to graphics describing computer simulations. Thus, I would like to = name them as meaningfully as possible, for instance simul001_a-4_b-0.1.pdf,= which would indicate that parameter a was fixed at 4 and parameter b at 0.= 1 for the first simulation.

In the org file, it would lo= ok like this:
#+latex_header: \graphicspath{ {./images/} }
[[file:simul001_a-4_b-0.1.pdf]]

After doing C-c C-e = l l, the tex file would look like that:
...
\includegraphics[width=3D= .9\linewidth]{simul001_a-4_b-0.1.pdf}
...

However, after C-c = C-e l p, it doesn't work. Instead of the image, the pdf contains the fo= llowing sentence, _a-4_b-0.1.pdf _a-4_b-0.1.pdf.

I tested= with "simul001.pdf", and it works smoothly.

I = tested with "simul001_a_4_b_0_1.pdf", and it doesn't work. In= stead of the image, the pdf contains the following sentence, _a_4_b_0_1.pdf= _a_4_b_0_1.pdf, followed by an empty box containg somethign like simul001\= unhbox \voidb@x \penalty \@M \hskip \z@skip.

I= know that LaTeX doesn't like special characters in file names to inclu= de. However, I thought that underscores and hyphens were ok. As I guess I&#= 39;m not the only one who wants to name his files meaningfully, I wonder ho= w other people do. Would anyone have any idea?

TF
--047d7bb0498e7f0bf1050e5fdd3e--