all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Belohrad <david@belohrad.ch>
To: org-mode <emacs-orgmode@gnu.org>
Subject: beamer export and links with spaces
Date: Fri, 12 Feb 2016 09:57:18 +0100	[thread overview]
Message-ID: <uaxmvr6i9w1.fsf@beesknees.cern.ch> (raw)

Dear All,

i'm using org documents export to beamer. Recently I've changed my directory structures for the screenshots such, that they are located under date subdirectories, e.g.:

screenshots/22 January 2016/140808_21161vUU.png


If I'm going org-type beamer document, I was always using this type of declaration to export the figure:

** Summary from previous session
#+BEGIN_CENTER
#+ATTR_LaTeX: :width 0.8\linewidth
[[file:screenshots/22%20January%202016/140808_21161vUU.png]]
#+END_CENTER

as you can see, the spaces are replaced by %20, which is perfectly fine if browsing the file in emacs and clicking on the link. The image is correctly opened.

This however does not work when beamer/latex is exported, as the org snippet gets translated into:


\section{Summary from previous session}
\label{sec:orgheadline2}
\begin{frame}[label={sec:orgheadline1}]{Summary from previous session}
\begin{center}
\includegraphics[width=0.8\linewidth]{screenshots/22%20January%202016/140808_21161vUU.png}
\end{center}
\end{frame}

hence the includegraphics does not contain space, but contains %20. Such file cannot be found.

What is the way to make it working? It seems that includegraphics generally does not like spaces inside unless one uses e.g. grffile, so the problem could be resolved just by replacing %20 in the latex output by an ordinary space and including \usepackage[space]{grffile}.

any hint?

thanks
.d.

             reply	other threads:[~2016-02-12  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12  8:57 David Belohrad [this message]
2016-02-12 10:00 ` beamer export and links with spaces Eric S Fraga

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uaxmvr6i9w1.fsf@beesknees.cern.ch \
    --to=david@belohrad.ch \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.