From: Bastien <bzg@altern.org>
To: David Maus <dmaus@ictsoc.de>
Cc: "R. Michael Weylandt <michael.weylandt@gmail.com>"
<michael.weylandt@gmail.com>, David Maus <maus.david@gmail.com>,
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: Sun, 25 May 2014 09:18:33 +0200 [thread overview]
Message-ID: <87fvjy5nsm.fsf@bzg.ath.cx> (raw)
In-Reply-To: <8761kuxrk1.wl%dmaus@ictsoc.de> (David Maus's message of "Sun, 25 May 2014 09:09:50 +0200")
Hi David,
David Maus <dmaus@ictsoc.de> writes:
> I can only speculate why they were escaped in the first place: + ; and
> = do have special meaning in HTTP URIs and IIRC Org did not draw a
> strict distinction between escaping for internal purposes and escaping
> of HTTP URIs.
Yes, that's certainly it -- thanks for enlightening me on this.
+ ; and = are not the only reserved characters, cf. RFC 3986 mentions
# @ and others that we don't escape. So I think we're good here.
Best,
--
Bastien
next prev parent reply other threads:[~2014-05-25 7:18 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>
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 [this message]
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
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=87fvjy5nsm.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=maus.david@gmail.com \
--cc=michael.weylandt@gmail.com \
/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).