From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Moritz_Sch=C3=A4fer?= Subject: Latex export from org-download images with spaces fails Date: Mon, 12 Nov 2018 09:52:20 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000561dda057a73d2d5" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gM85W-0004dR-No for emacs-orgmode@gnu.org; Mon, 12 Nov 2018 04:01:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gM85R-0004YN-Hm for emacs-orgmode@gnu.org; Mon, 12 Nov 2018 04:00:54 -0500 Received: from edge10.ethz.ch ([82.130.75.186]:21172) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gM85K-0004DT-Kp for emacs-orgmode@gnu.org; Mon, 12 Nov 2018 04:00:45 -0500 Received: by mail-qk1-f169.google.com with SMTP id o125so11972882qkf.3 for ; Mon, 12 Nov 2018 00:52:33 -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" To: emacs-orgmode@gnu.org --000000000000561dda057a73d2d5 Content-Type: text/plain; charset="UTF-8" Hello mailing list, when I use org-download to take a screenshot and automatically import the image into my org document it often contains spaces (because the overlying headline contains spaces and the image gets saved in a folder with the same name). org-download seems to use URL encoding when storing the link in the org file so these spaces get converted to "%20". Org-mode seems to be fine with this and calling org-toggle-inline-images the image as shown as expected. However, when exporting to LaTex, the images are not shown in the resulting PDF file (which can recovered by changing the URL encoded spaces to real spaces). I now wonder which module is the problem here: - Should LaTex be able to understand URL encoded paths? - Are URL encoded links normal/encourged in org-mode? - Should org-download use normal spaces instead of URL encoding? I'm happy for any suggestion you have on how to workarround this and on where I should file a bug report. I started at org-download ( https://github.com/abo-abo/org-download/issues/84) Thanks for your help --000000000000561dda057a73d2d5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello mailing list,

when I use org-download to take a screenshot and automatically imp= ort the image into my org document it often contains spaces (because the ov= erlying headline contains spaces and the image gets saved in a folder with = the same name).
org-download seems to use URL encoding when stori= ng the link in the org file so these spaces get converted to "%20"= ;. Org-mode seems to be fine with this and calling org-toggle-inline-images= the image as shown as expected.

However, when exp= orting to LaTex, the images are not shown in the resulting PDF file (which = can recovered by changing the URL encoded spaces to real spaces).=C2=A0

I now wonder which module is the problem here:
<= div>- Should LaTex be able to understand URL encoded paths?
- Are= URL encoded links normal/encourged in org-mode?
- Should org-dow= nload use normal spaces instead of URL encoding?

I= 'm happy for any suggestion you have on how to workarround this and on = where I should file a bug report. I started at org-download (https://github.com/abo-abo/= org-download/issues/84)

Thanks for your help
--000000000000561dda057a73d2d5--