From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Thum Subject: Re: Org-link-escape-chars (was Incorrect hexification in URLs in LaTeX Export) Date: Mon, 17 Mar 2014 13:24:24 +0100 Message-ID: <5326E978.2020702@gmx.de> References: <0DEDD4E4-A513-4B03-AA78-25D9859EEA9F@gmail.com> <87fvn32dcm.fsf@med.uni-goettingen.de> <4846AB82-370A-48F1-97DC-6319ECA261A5@gmail.com> <53163B6A.5000200@gmx.de> <87y50nele8.fsf@med.uni-goettingen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48586) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPWao-0005MW-EV for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 08:24:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPWai-0003gm-93 for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 08:24:34 -0400 Received: from mout.gmx.net ([212.227.15.15]:56751) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPWai-0003gH-0A for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 08:24:28 -0400 In-Reply-To: <87y50nele8.fsf@med.uni-goettingen.de> 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: Andreas Leha , emacs-orgmode@gnu.org Hehe ;) No, I was merely suggesting that maybe someone tried too hard to fix non-working urls becauase of other use cases. Luckily it seems fixed now. On 03/06/2014 10:17 AM, Andreas Leha wrote: > "R. Michael Weylandt" writes: > >> On Tue, Mar 4, 2014 at 3:45 PM, Simon Thum wrote: >>> This seems to be a question of objective. Do you want to encode, i.e. >>> maintain some reversible original in an url no matter what, or do you want >>> to fix url's which wouldn't otherwise be legal? In the latter case, the >>> question mark should probably be retained. >>> > > I am not sure, that I understand what you say here. But in case you > want to convince me, that exporting non-working links when the user > supplies working links is a feature and not a bug, you will have a hard > time ;-) > > - Andreas > >> >> I believe the former. If the user types in a working link, the >> exporter shouldn't break it. >> >> This could be fixed by sprinkling org-url-decode through various >> backends, but that suggests to me that the problem may be "upstream." >> >> Michael > > >