emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Eduardo Mercovich <eduardo@mercovich.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: LaTeX > PDF blocked by extender chars in filename
Date: Sat, 26 Aug 2017 08:39:41 -1000	[thread overview]
Message-ID: <m2efryi36a.fsf@tsdye.com> (raw)
In-Reply-To: <87efryi40n.fsf@biologica.mercovich.net>

Aloha Eduardo,

In my experience, having both org and org-plus-contrib installed is a
problem.  You might want to settle on the one or the other, then see if
your problem persists.

hth,
Tom

Eduardo Mercovich writes:

> Hola Nicolas.
>
>>> The file > img/ProcesoDeDiseñoDeInteraccion.pdf
>>> was translated/inserted on the org buffer as >
>>> img/ProcesoDeDise%C3%B1oDeInteraccion.pdf
>
>> What command did you use to "translate/insert" the filename?
>
> C-c C-l with keyboard and tab completion.
>
>>> + Org-mode: Org-mode version 8.3.4 (8.3.4-88-g792bb9-elpaplus)
>
>> This release is old. Could you update to a more recent one?
>
> Sure. Upgraded from the package manager and now I have
> org-20170821 and org-plus-contrib-20170821. Both from elpa. Would
> it be better from the org repository?
>
> org-version gives: Org mode version 9.0.9
> (9.0.9-88-g251f88-elpaplus [...])
>
>
> Repeating the same experiment now results in:
>
> 1. Org inserts the same string
> (file:img/ProcesoDeDise%C3%B1oDeInteraccion.pdf)
>
> 2. But export is not blocked! :)
>
> 3. The linked file is not present on the exported pdf (may not be
> an org issue, but about other latex to pdf component)...
>
> I hope this is useful.
> How do I proceed from here? Any other test or info to report?
>
> Thanks a lot for your hard work on Org. :)


--
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2017-08-26 18:52 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 [this message]
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
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=m2efryi36a.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=eduardo@mercovich.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).