From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabrice Popineau Subject: Re: Links Date: Tue, 16 Jun 2015 15:32:28 +0200 Message-ID: References: <87wpz3akc4.fsf@selenimh.access.network> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1130caea4c1d620518a29c3e Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4qyx-0007Fa-LK for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 09:32:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z4qyw-0003eT-Az for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 09:32:51 -0400 Received: from mail-oi0-x22d.google.com ([2607:f8b0:4003:c06::22d]:36726) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4qyw-0003eP-6e for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 09:32:50 -0400 Received: by oial131 with SMTP id l131so11243785oia.3 for ; Tue, 16 Jun 2015 06:32:49 -0700 (PDT) In-Reply-To: <87wpz3akc4.fsf@selenimh.access.network> 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: Fabrice Popineau , "emacs-orgmode@gnu.org" --001a1130caea4c1d620518a29c3e Content-Type: text/plain; charset=UTF-8 2015-06-16 14:50 GMT+02:00 Nicolas Goaziou : > Hello, > > > So, export process doesn't url-decode links, and cannot handle the link > above. This is what I was missing :-) > At this point, it seems that all is left are cheesy approaches. E.g, > when a path matches "%[A-Za-z0-9]\\{2\\}", decode it during export. This > leaves pathological cases (e.g., when you really meant, for some very > good reason, to have a headline called "* %25"), though. That's not > great either. > > WDYT? > I don't know what is realistic. I see the tradeoffs are tight. Ideally, url encoded links should have been prefixed with some kind of uri syntax. This way, you could know what to decode and what not. Now, I guess the heuristic you propose would be fine in most cases. I don't see that people will put a lot of percentages in their links. Thanks for the explanations ! Fabrice > Regards, > > -- > Nicolas Goaziou > --001a1130caea4c1d620518a29c3e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-06-16 14:50 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.f= r>:
Hello,


So, export process doesn't url-decode links, and cannot handle the link=
above.

This is what I was missing :-)
=
=C2=A0
At this point, it seems that all is left are cheesy approaches. E.g,
when a path matches "%[A-Za-z0-9]\\{2\\}", decode it during expor= t. This
leaves pathological cases (e.g., when you really meant, for some very
good reason, to have a headline called "* %25"), though. That'= ;s not
great either.

WDYT?

I don't know what is realisti= c. I see the tradeoffs are tight.

Ideally, url enc= oded links should have been prefixed with some kind of uri syntax.
This way, you could know what to decode and what not.

Now, I guess the heuristic you propose would be fine in most cases.
I don't see that people will put a lot of percentages in their= links.

Thanks for the explanations !
Fabrice
=C2=A0
Regards,

--
Nicolas Goaziou

--001a1130caea4c1d620518a29c3e--