From: "R. Michael Weylandt <michael.weylandt@gmail.com>" <michael.weylandt@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Incorrect hexification in URLs in LaTeX Export
Date: Tue, 18 Mar 2014 17:24:37 -0400 [thread overview]
Message-ID: <43DB32AC-723C-4046-9DCD-4A1FD2DD7323@gmail.com> (raw)
In-Reply-To: <87ppljfr99.fsf@bzg.ath.cx>
On Mar 18, 2014, at 11:41, Bastien <bzg@gnu.org> wrote:
> Hi Andreas,
>
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> The second link is not clickable in the resulting pdf.
>
> This should be fixed now, thanks.
>
Hi Bastien,
I just tried with 35f27a1fe and my issue is fixed. (The one about the hexifying of a valid character. I.e., if (fundamental-mode) shows a valid link, the resulting export is also valid)
Can't comment on Andreas's issue about unescaping text when it's given to org already escaped.
Thanks,
Michael
next prev parent reply other threads:[~2014-03-18 21:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 18:51 Incorrect hexification in URLs in LaTeX Export R. Michael Weylandt <michael.weylandt@gmail.com>
2014-02-28 20:26 ` Andreas Leha
2014-03-03 20:06 ` Org-link-escape-chars (was Incorrect hexification in URLs in LaTeX Export) R. Michael Weylandt <michael.weylandt@gmail.com>
2014-03-04 20:45 ` Simon Thum
2014-03-06 2:58 ` R. Michael Weylandt
2014-03-06 9:17 ` Andreas Leha
2014-03-17 12:24 ` Simon Thum
2014-03-12 18:47 ` Incorrect hexification in URLs in LaTeX Export Bastien
2014-03-17 21:31 ` Andreas Leha
2014-03-18 15:41 ` Bastien
2014-03-18 21:24 ` R. Michael Weylandt <michael.weylandt@gmail.com> [this message]
2014-03-19 14:37 ` R. Michael Weylandt <michael.weylandt@gmail.com>
2014-05-25 5:56 ` Bastien
2014-05-25 7:09 ` David Maus
2014-05-25 7:18 ` Bastien
2014-05-25 7:22 ` David Maus
2014-05-26 5:16 ` Bastien
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=43DB32AC-723C-4046-9DCD-4A1FD2DD7323@gmail.com \
--to=michael.weylandt@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=bzg@gnu.org \
--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.