From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suvayu Ali Subject: Re: Target and link text normalised to `orgtargetn' Date: Sun, 19 Apr 2015 14:13:05 +0200 Message-ID: <20150419121305.GZ14328@chitra.no-ip.org> References: <20150414092530.GC2957@chitra.no-ip.org> <20150414120852.GD2957@chitra.no-ip.org> <87zj699ez9.fsf@gmx.us> <20150416001830.GC14328@chitra.no-ip.org> <87egnk9ycz.fsf@gmx.us> <87k2x9cddu.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46564) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yjo65-0001WE-QB for emacs-orgmode@gnu.org; Sun, 19 Apr 2015 08:13:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yjo62-0007w9-KX for emacs-orgmode@gnu.org; Sun, 19 Apr 2015 08:13:13 -0400 Received: from mail-wg0-x235.google.com ([2a00:1450:400c:c00::235]:34421) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yjo62-0007vr-D8 for emacs-orgmode@gnu.org; Sun, 19 Apr 2015 08:13:10 -0400 Received: by wgso17 with SMTP id o17so153369152wgs.1 for ; Sun, 19 Apr 2015 05:13:09 -0700 (PDT) Content-Disposition: inline In-Reply-To: <87k2x9cddu.fsf@nicolasgoaziou.fr> 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: emacs-orgmode@gnu.org Cc: Rasmus Hi Nicolas, On Sat, Apr 18, 2015 at 11:53:01PM +0200, Nicolas Goaziou wrote: > Hello, > > Rasmus writes: > > > Suvayu Ali writes: > > > >> Hi Rasmus, > >> > >> On Thu, Apr 16, 2015 at 12:57:46AM +0200, Rasmus wrote: > >>> > >>> Could you try the attached patches and see if they solve your issues? > >> > >> Seems to work nicely. I'll keep using them rest of the week. > > > > Pushed. > > > > I removed support for radio targets as I don't really see the point in > > those supporting custom labeling. They are transcoded as > > > > <<> > > → > > \hyperref{label}{target} > > > > It makes little sense to label be the same as target, though it probably > > would not create problems. > > I don't see the point of this change. The naming scheme is internal > anyway. Users are not supposed to use it directly. Sorry, I don't think I quite understand. AFAIU, targets like <> have to be unique even inside the Org buffer for links like this to work: [[interesting][very cool]], regardless of export. So then why rename them during export? > If you want \label{foo} in the output, you can write > @@latex:\label{foo}@@. > > Targets are for Org links and are expected to work across all back-ends, > so the problem they solve is slightly different. How does the above solve the issue? I was not having problems with getting to export \label{foo}, my problem was what do I put as `foo' since in the exported TeX file foo was different. Hopefully I made myself clear, or I'm not misunderstanding something. Cheers, -- Suvayu Open source is the future. It sets us free.