From: Eduardo Mercovich <eduardo@mercovich.net>
To: Adonay Felipe Nogueira <adfeno@hyperbola.info>
Cc: emacs-orgmode@gnu.org
Subject: Re: LaTeX > PDF blocked by extender chars in filename
Date: Wed, 30 Aug 2017 17:29:49 -0300 [thread overview]
Message-ID: <87pobcyf2a.fsf@biologica.mercovich.net> (raw)
In-Reply-To: <873789os4x.fsf@hyperbola.info>
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)
next prev parent reply other threads:[~2017-08-30 20:30 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pobcyf2a.fsf@biologica.mercovich.net \
--to=eduardo@mercovich.net \
--cc=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 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.