From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: org-exp-bibtex missing in git? Date: Wed, 06 Mar 2013 23:55:30 +0100 Message-ID: <87mwugqgt9.fsf@bzg.ath.cx> 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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDNFI-0001fS-7h for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 17:55:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDNFH-0004xy-2E for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 17:55:36 -0500 Received: from mail-wg0-f52.google.com ([74.125.82.52]:36199) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDNFG-0004xt-Rv for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 17:55:34 -0500 Received: by mail-wg0-f52.google.com with SMTP id 12so8478363wgh.7 for ; Wed, 06 Mar 2013 14:55:33 -0800 (PST) In-Reply-To: <87obewe5jy.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 06 Mar 2013 19:39:29 +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: Andreas Leha , emacs-orgmode@gnu.org 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? 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. -- Bastien