From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: emacs-orgmode@gnu.org
Subject: Re: LaTeX > PDF blocked by extender chars in filename
Date: Wed, 30 Aug 2017 14:57:34 -0300 [thread overview]
Message-ID: <873789os4x.fsf@hyperbola.info> (raw)
In-Reply-To: <87a82hf1au.fsf@biologica.mercovich.net> (Eduardo Mercovich's message of "Wed, 30 Aug 2017 13:49:45 -0300")
This somehow happens to be problematic to me too, if for some reason the
inclusion of the file isn't made by Org mode itself.
For example, we know that "#+INCLUDE:" keywords at the start of the line
are Org mode specific includes, and you can place the file references in
the first argument with the literal characters (that is: no need to do
percent encoding/escaping).
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).
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.
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.
Hope this helps! :)
--
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre. Por favor, use o GNU Ring ou o Tox.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
(apenas sem DRM), PNG, TXT, WEBM.
next prev parent reply other threads:[~2017-08-30 17:57 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 [this message]
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
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873789os4x.fsf@hyperbola.info \
--to=adfeno@hyperbola.info \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).