From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eduardo Mercovich <eduardo@mercovich.net>
Cc: emacs-orgmode@gnu.org, Adonay Felipe Nogueira <adfeno@hyperbola.info>
Subject: Re: LaTeX > PDF blocked by extender chars in filename
Date: Thu, 31 Aug 2017 16:06:21 +0200 [thread overview]
Message-ID: <87wp5j4ysi.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87val329lb.fsf@biologica.mercovich.net> (Eduardo Mercovich's message of "Thu, 31 Aug 2017 09:41:20 -0300")
Hello,
Eduardo Mercovich <eduardo@mercovich.net> writes:
> Rounding up:
> + if we include the grffilesetup options "{filenameencoding = utf8,
> space}", and
> + insert the filename as it is,
> + the pdf is exported and the referenced file is correctly included.
>
> Nicolas, does this means we should modify these little things in Org?
Unfortunately these are not "little things".
First, I assume "filenameencoding" is not necessarily utf8, so it cannot
be a default value.
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.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-08-31 14:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 19:43 LaTeX > PDF blocked by extender chars in filename Eduardo Mercovich
2017-08-25 20:03 ` Nicolas Goaziou
2017-08-26 18:21 ` Eduardo Mercovich
2017-08-26 18:39 ` Thomas S. Dye
2017-08-27 17:43 ` Eduardo Mercovich
2017-08-30 15:02 ` Nicolas Goaziou
2017-08-30 16:49 ` Eduardo Mercovich
2017-08-30 17:57 ` Adonay Felipe Nogueira
2017-08-30 20:29 ` Eduardo Mercovich
2017-08-30 22:30 ` Adonay Felipe Nogueira
2017-08-31 12:41 ` Eduardo Mercovich
2017-08-31 14:06 ` Nicolas Goaziou [this message]
2017-08-31 14:24 ` Eduardo Mercovich
2017-09-01 10:21 ` Rasmus
2017-09-01 11:55 ` Adonay Felipe Nogueira
2017-09-01 12:02 ` Adonay Felipe Nogueira
2017-09-01 13:03 ` Eduardo Mercovich
2017-09-13 13:22 ` Adonay Felipe Nogueira
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=87wp5j4ysi.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=adfeno@hyperbola.info \
--cc=eduardo@mercovich.net \
--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.