From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Radio targets with mixed capitalisation do not work in HTML export Date: Mon, 17 Mar 2014 16:50:47 +0100 Message-ID: <87a9coj02w.fsf@bzg.ath.cx> References: <874n2xlgzx.fsf@bzg.ath.cx> <87eh21qgmh.fsf@gmail.com> <87d2hlhxm2.fsf@bzg.ath.cx> <87zjkpghff.fsf@bzg.ath.cx> <87vbvcq4rj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52256) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPZpC-00067K-GN for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 11:52:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPZoS-0003eL-7u for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 11:51:38 -0400 Received: from rs249.mailgun.us ([209.61.151.249]:49365) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPZoS-0003dq-2h for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 11:50:52 -0400 In-Reply-To: <87vbvcq4rj.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 17 Mar 2014 15:27:44 +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: Noah Slater , emacs-orgmode@gnu.org Hi Nicolas, Nicolas Goaziou writes: > path is always a string. Description is always parsed (and transcoded > already). In the most simple cases, they are equals. I found out I have to parse the path because "hello \alpha" would not be exported correctly otherwise. (But I agree this is a corner case.) > 5174495 adds contents to radio links (and, because of this, introduces > an infloop in `org-element-context' on master, but that's another > story). Your change parses link's contents on the fly. So this is mostly > equivalent, albeit more verbose in all exporters. Yes, I parsed the link's contents on the fly just for the purpose of this small patch, but a general solution is better. > So the question is : should we consider a radio-link as a link with > a description, which would basically be its parsed path? I think so. > I think it is > useful because its contents can differ from its relative radio-target, > due to case-insensitivity. Indeed. Can you make the change (ie. radio-link is a link with a description, the description being its parsed path)? If so, do you want me to make the change in the backends or do you want to take care of this too? Thanks, -- Bastien