From: David Maus <dmaus@ictsoc.de>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: David Maus <dmaus@ictsoc.de>,
emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>,
Nick Dokos <ndokos@gmail.com>
Subject: Re: Encoding Problem in export?
Date: Sun, 28 Jul 2013 13:16:35 +0200 [thread overview]
Message-ID: <8761vv2auk.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <87bo5n84ih.fsf@gmail.com>
At Sun, 28 Jul 2013 14:06:54 +0530,
Jambunathan K wrote:
>
>
> If Org links are escaped by Org will the URLs be functional outside of
> Org?
>
> i.e., If I am on some machine, that has no Emacs or Org or if I am using
> a version of Org that uses "new unescape" algorithm but the original
> link was encoded with the "old escape" algorithm, will Copy-pasting the
> link to a browser still work.
I think this is a good point or rather two good points: One is BC. If
we change the escaping algorithm we still have to deal with possibly
tons of old-style-links in user files.
The other one is that leaving the edge cases aside it is possible to
just copy a link and paste it into the target application -- a percent
sign signifies percent encoding and the target application knows what
to do.
> If Org is a MUST to unescape the link then it would be a good decision
> to re-look at the link syntax so that the questions of escape and
> un-escape is dealt with squarely and have no reasons to arise in future.
>
I'm not sure if it is worth the effort but, in theory, we could do
define our own URI schema `org' that disallows square brackets. If a
link is created programmatically (org-store-link et al.) we do not
store the URI as-is but as an "Orgmode-Link": Escape the square
brackets and prefix the link with `org:'. If we open a link we check
for the `org:'-prefix, reverse the escaping and handle the link to the
registered module. If the prefix is absent we skip the unescaping
step.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
next prev parent reply other threads:[~2013-07-28 11:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 23:17 Encoding Problem in export? Robert Eckl
2013-07-23 23:35 ` Nicolas Goaziou
2013-07-24 1:50 ` Robert Eckl
2013-07-24 7:34 ` Nicolas Goaziou
2013-07-24 8:46 ` Robert Eckl
2013-07-24 9:16 ` Nicolas Goaziou
2013-07-24 10:27 ` Robert Eckl
2013-07-24 9:39 ` Nick Dokos
2013-07-24 11:09 ` Nicolas Goaziou
2013-07-25 4:05 ` David Maus
2013-07-25 21:46 ` Nicolas Goaziou
2013-07-26 4:03 ` David Maus
2013-07-26 10:20 ` Nicolas Goaziou
2013-07-27 7:23 ` David Maus
2013-07-27 11:09 ` Nicolas Goaziou
2013-07-28 8:36 ` Jambunathan K
2013-07-28 8:54 ` Jambunathan K
2013-07-28 11:16 ` David Maus [this message]
2013-07-28 11:22 ` Nicolas Goaziou
2013-07-29 6:59 ` Jambunathan K
2013-11-16 15:16 ` Michael Brand
2013-11-16 20:43 ` Nicolas Goaziou
2013-11-17 11:06 ` Michael Brand
2013-11-17 11:46 ` Nicolas Goaziou
2013-11-17 11:51 ` Michael Brand
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=8761vv2auk.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=n.goaziou@gmail.com \
--cc=ndokos@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).