From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Bug: HTML Export doesn't handle internal link with spaces [8.0.7 (8.0.7-6-g13cb28-elpa @ /home/jbalint/.emacs.d/elpa/org-20130812/)] Date: Sun, 05 Jan 2014 07:45:18 +0100 Message-ID: <874n5jvse9.fsf@bzg.ath.cx> References: <87zjo034l8.wl%jbalint@gmail.com> <87sitnjit3.fsf@gmail.com> <87r48pce92.fsf@bzg.ath.cx> <8738l5ds2n.fsf@gmail.com> <87r48nstkt.fsf@bzg.ath.cx> <87r48nmh0i.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60118) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzhSl-0000m3-Sx for emacs-orgmode@gnu.org; Sun, 05 Jan 2014 01:45:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VzhSd-0002CA-F4 for emacs-orgmode@gnu.org; Sun, 05 Jan 2014 01:45:31 -0500 Received: from mail-wg0-x230.google.com ([2a00:1450:400c:c00::230]:60522) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzhSd-0002C6-62 for emacs-orgmode@gnu.org; Sun, 05 Jan 2014 01:45:23 -0500 Received: by mail-wg0-f48.google.com with SMTP id z12so14822745wgg.27 for ; Sat, 04 Jan 2014 22:45:22 -0800 (PST) In-Reply-To: <87r48nmh0i.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 05 Jan 2014 01:03:41 +0100") 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org, Jess Balint Nicolas Goaziou writes: > I'm not sure to understand. IIUC, one reason for url-hexification is to > avoid forbidden characters in Org links, i.e., Org hexifies links to > escape characters like brackets. > > Do you mean using another escape mechanism? No, I mean to url-hexify URLs that correspond to a link type (through org-link-types) and for internal links, to escape only [ and ], which are the only two problematic characters (aren't they?) > If so, I think the problem > would be the same as before (impossible to know if link at point was > escaped or not in the first place). Yes... > Another idea would be to get rid of automatic hexification in all cases, > and have more tolerant regexps for links. This seems incertain. Or maybe we can just live with the current problem. -- Bastien