From: "R. Michael Weylandt <michael.weylandt@gmail.com>" <michael.weylandt@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Incorrect hexification in URLs in LaTeX Export
Date: Fri, 28 Feb 2014 13:51:23 -0500 [thread overview]
Message-ID: <0DEDD4E4-A513-4B03-AA78-25D9859EEA9F@gmail.com> (raw)
I've tried this with Org 7.9.3 and 8.2.5h to the same result:
<---------------------->
#+TITLE: Test
* One
Here is a [[http://google.com/search?q=orgmode][link]]
<---------------------->
Exporting to HTML doesn't transform the link but exporting to LaTeX results in the (non-working) http://google.com/search?%3Dorgmode
Is there a reason for this behavior and, if so, a way to work around it?
RFC 3986 2.2 explicitly says URLs may include `=` and =url-encode-url= doesn't change the link in question.
I've played with org-url-hexify-p and read past ML discussions, but they seem primarily concerned with characters which should not appear in URIs.
Thanks,
Michael
next reply other threads:[~2014-02-28 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 18:51 R. Michael Weylandt <michael.weylandt@gmail.com> [this message]
2014-02-28 20:26 ` Incorrect hexification in URLs in LaTeX Export 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>
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=0DEDD4E4-A513-4B03-AA78-25D9859EEA9F@gmail.com \
--to=michael.weylandt@gmail.com \
--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.