From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Mercovich Subject: Re: LaTeX > PDF blocked by extender chars in filename Date: Wed, 30 Aug 2017 17:29:49 -0300 Message-ID: <87pobcyf2a.fsf@biologica.mercovich.net> References: <87fucgoiob.fsf@biologica.mercovich.net> <87k21rxvml.fsf@nicolasgoaziou.fr> <87efryi40n.fsf@biologica.mercovich.net> <87a82hnlo1.fsf@nicolasgoaziou.fr> <87a82hf1au.fsf@biologica.mercovich.net> <873789os4x.fsf@hyperbola.info> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56245) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dn9d2-000181-IC for emacs-orgmode@gnu.org; Wed, 30 Aug 2017 16:30:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dn9cy-00027S-JH for emacs-orgmode@gnu.org; Wed, 30 Aug 2017 16:30:24 -0400 Received: from mail-qk0-x235.google.com ([2607:f8b0:400d:c09::235]:34177) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dn9cy-00027F-E5 for emacs-orgmode@gnu.org; Wed, 30 Aug 2017 16:30:20 -0400 Received: by mail-qk0-x235.google.com with SMTP id a77so32922413qkb.1 for ; Wed, 30 Aug 2017 13:30:20 -0700 (PDT) In-reply-to: <873789os4x.fsf@hyperbola.info> 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: Adonay Felipe Nogueira Cc: emacs-orgmode@gnu.org Dear Felipe. > This somehow happens to be problematic to me too [...] However, > hyperlinks (that is: those between "[[" and "]]") demand percent > encoding/escaping. But, it seems that the Org-to-LaTeX exporter > isn't translating the hyperlinks to something LaTeX understands > (LaTeX expects literal characters, and "%" is the start of a > comment). Great finding, this seems like a possible culprit... > Also, as a final note, the default grffile inclusion in the > Org-to-LaTeX (and to PDF also) doesn't include the necessary > options to make LaTeX accept spaces and accents in file names. > That's OK for compatibility reasons, and if you do want to force > it to accept such special characters, use the grffilesetup LaTeX > command with the proper grffile options. I didn't knew about grffile, thanks. So, does this means that to support extended ascii chars we need to include this package? > Personally, I like to go the safest route: remove special > characters from file names whenever I don't need them. I > generally replace spaces with underscores, and leave letters > without accent. This also avoids having to deal with the broken > percent decoding/unescaping when doing Org-to-LaTeX exports. I also do that usually. I found this case because a special char (ñ) escaped me. ;) However, given the widespread use of extended ascii chars in many languages around the world (and the excellent support that emacs in particular and the free/libre software movement in general are proud to have for them) it would be good to have something as this working without glitches. Also, it may be a showstopper for newbies since it may take quite a while to find what is happening. After all, if there is no problem with my OS, why would it be an issue with emacs? Except programming that I don't know how to do, I would gladly do what it takes to help with this. :) Thanks Nicolas and Felipe for your attention... :D -- eduardo mercovich Donde se cruzan tus talentos con las necesidades del mundo, ahí está tu vocación. (Anónimo)