From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Leha Subject: Re: org-exp-bibtex missing in git? Date: Thu, 07 Mar 2013 00:37:16 +0100 Message-ID: <87ip54drrn.fsf@med.uni-goettingen.de> References: <20130303070635.GA12112@panahar> <87fw0cg42y.fsf@allisson.co> <87vc98be83.fsf@bzg.ath.cx> <87ehfwwgdd.fsf@gmail.com> <87ppzg2r05.fsf@med.uni-goettingen.de> <87ppzgusem.fsf@gmail.com> <87ppzcfy2e.fsf@med.uni-goettingen.de> <87lia0s7wi.fsf@bzg.ath.cx> <87obewe5jy.fsf@gmail.com> <87mwugqgt9.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48216) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDNw2-0004v1-AD for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 18:39:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDNw0-0001iy-Db for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 18:39:46 -0500 Received: from plane.gmane.org ([80.91.229.3]:57778) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDNw0-0001ip-3r for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 18:39:44 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UDNwK-0000oZ-DH for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 00:40:04 +0100 Received: from vpn-2097.gwdg.de ([134.76.2.97]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 07 Mar 2013 00:40:04 +0100 Received: from andreas.leha by vpn-2097.gwdg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 07 Mar 2013 00:40:04 +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: emacs-orgmode@gnu.org Hi Bastien, Bastien writes: > Hi Nicolas, > > Nicolas Goaziou writes: > >> If we're not going to provide a multi-backend solution, I suggest to >> keep things simple and write LaTeX code directly (or use the solution >> provided by Eric). Unless you have something else in mind with these >> link abbrevs, of course. > > Can you resend me the link to Eric's suggestion? http://permalink.gmane.org/gmane.emacs.orgmode/67574 > > Actually my suggestion is multi-backends ready: I gave an example for > `org-latex-bibtex-link', but `org-html-bibtex-link' could be used at > the same place. > > The link export mechanism would be in charge to select the right > function when there are several. If there is no backend-specific > function, the exporter would fall back on the normal export mechanism > for links. > > The trick would just be to attach the available functions (possibly > multiple ones, for the various backends) as properties to the links > (aka :latex-link-function for the :link object in the internal > representation) and to select the correct function depending on the > export backend. > > Do it make (some) sense? The idea is to *not* add a new link type > with a new syntax, but to rely on the abbreviated links, which I > think are flexible enough. To give some un-qualified comment: As far as I understand your suggestion, I like it from the technical point of view. But it looks very verbose to me. I expect the introduction to a scientific paper (with typically many \cite{}s) to look disrupted. Regards, Andreas