From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Encoding Problem in export? Date: Sun, 28 Jul 2013 13:22:45 +0200 Message-ID: <87ehaj0vzu.fsf@gmail.com> References: <87bo5s27ey.fsf@sachwertpartner.de> <877ggg7suh.fsf@gmail.com> <51EF32F4.9030309@gmx.de> <87txjk5s2q.fsf@gmail.com> <87a9lcfg9g.fsf@gmail.com> <877ggg5i5q.fsf@gmail.com> <87y58vp9mj.wl%dmaus@ictsoc.de> <87li4u48jp.fsf@gmail.com> <87r4emdl2a.wl%dmaus@ictsoc.de> <87d2q54o7e.fsf@gmail.com> <87k3kc1n6f.wl%dmaus@ictsoc.de> <87iozwmf87.fsf@gmail.com> <87bo5n84ih.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34961) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V3P3q-0007pj-F5 for emacs-orgmode@gnu.org; Sun, 28 Jul 2013 07:22:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V3P3b-0001sM-8w for emacs-orgmode@gnu.org; Sun, 28 Jul 2013 07:22:50 -0400 Received: from mail-wg0-x229.google.com ([2a00:1450:400c:c00::229]:45621) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V3P3b-0001sB-2F for emacs-orgmode@gnu.org; Sun, 28 Jul 2013 07:22:35 -0400 Received: by mail-wg0-f41.google.com with SMTP id n11so1993581wgh.0 for ; Sun, 28 Jul 2013 04:22:33 -0700 (PDT) In-Reply-To: <87bo5n84ih.fsf@gmail.com> (Jambunathan K.'s message of "Sun, 28 Jul 2013 14:06:54 +0530") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jambunathan K Cc: David Maus , emacs-orgmode@gnu.org, Nick Dokos Hello, Jambunathan K writes: > If Org links are escaped by Org will the URLs be functional outside of > Org? If there is an "unencoding" part, and if that part cannot happen for some reason, links will be unusable outside Org. That's already the case with the current encoding, which will break, for example, links already hexified if it cannot unencode them properly. > 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. We can also avoid any encoding, and extend link syntax so it allows balanced square brackets (with a maximum depth, otherwise we cannot use a regexp for bracket links anymore). Regards, -- Nicolas Goaziou