From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Mercovich Subject: Re: LaTeX > PDF blocked by extender chars in filename Date: Thu, 31 Aug 2017 11:24:58 -0300 Message-ID: <87tw0n24sl.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> <87pobcyf2a.fsf@biologica.mercovich.net> <87tw0on0y6.fsf@hyperbola.info> <87val329lb.fsf@biologica.mercovich.net> <87wp5j4ysi.fsf@nicolasgoaziou.fr> 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]:43629) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dnQP3-0008H4-Vi for emacs-orgmode@gnu.org; Thu, 31 Aug 2017 10:25:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dnQOz-0007iJ-Up for emacs-orgmode@gnu.org; Thu, 31 Aug 2017 10:25:05 -0400 Received: from mail-qk0-x230.google.com ([2607:f8b0:400d:c09::230]:34089) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dnQOz-0007i6-NR for emacs-orgmode@gnu.org; Thu, 31 Aug 2017 10:25:01 -0400 Received: by mail-qk0-x230.google.com with SMTP id a77so3480070qkb.1 for ; Thu, 31 Aug 2017 07:25:01 -0700 (PDT) In-reply-to: <87wp5j4ysi.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org, Adonay Felipe Nogueira Hello Nicolas. [...] >> Nicolas, does this means we should modify these little things >> in Org? > Unfortunately these are not "little things". Sorry, it was my ignorance of the infrastructure on which this depends... > First, I assume "filenameencoding" is not necessarily utf8, so > it cannot be a default value. Ah, super clear. > More importantly, there is an ongoing issue with link encoding, > which is debated in another (moribund) thread. IOW, "insert the > filename as it is" is not easy, because Org needs to encode file > names, but doesn't know for sure when a file name has been > encoded. Ok, got it. So, what should we do? Here are some possible things to discuss... + One thing that may be relatively simple to do (I won't assume "little things" anymore) is to warn in the documentation that for the moment, it's preferable to avoid extended chars in filenames. + Other point: is it logical to warn the User in the moment when the link is created, that we found extended chars and that may complicate things on the export? (I wouldn't recomend to change the filename even if from the HCI POV seems logical, since we don't know the origin of this filename, among other reasons, and could even be re-writed). + Does it make sense to check the files in the moment we write the latex file, and change the filename/s in that instant? Or at least to warn the User then? + Farther in the future is that decision about to encode or not the links, in which I can't emit any opinion since it is far from my domain. + Other possibilities? -- eduardo mercovich Donde se cruzan tus talentos con las necesidades del mundo, ahí está tu vocación. (Anónimo)