From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org-exp-bibtex missing in git? Date: Sat, 09 Mar 2013 16:15:01 +0100 Message-ID: <874ngkzjt6.fsf@gmail.com> 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> <876213lqfk.fsf@gmail.com> <87wqtjo6h6.fsf@bzg.ath.cx> <87boavcpzc.fsf@gmail.com> <87fw075ivl.fsf@bzg.ath.cx> <87wqthk7vj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51841) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UELUU-00087U-Er for emacs-orgmode@gnu.org; Sat, 09 Mar 2013 10:15:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UELUP-0004wH-LJ for emacs-orgmode@gnu.org; Sat, 09 Mar 2013 10:15:18 -0500 Received: from mail-wg0-f45.google.com ([74.125.82.45]:59641) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UELUP-0004w9-Ez for emacs-orgmode@gnu.org; Sat, 09 Mar 2013 10:15:13 -0500 Received: by mail-wg0-f45.google.com with SMTP id dq12so3620953wgb.12 for ; Sat, 09 Mar 2013 07:15:12 -0800 (PST) In-Reply-To: <87wqthk7vj.fsf@gmail.com> (aaronecay@gmail.com's message of "Fri, 08 Mar 2013 14:29:36 -0500") 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: Bastien Cc: Andreas Leha , emacs-orgmode@gnu.org Hello, aaronecay@gmail.com writes: >> I think that if we ever implement a bibliography/citations handlers, >> they should be first class objects in Org syntax (like footnotes). >> Overloading link syntax would, IMO, be wrong in that case. > > Do you have a proposal for how this syntax would look? You certainly > know the parser very well, so you probably have an idea of what will > work and not conflict with other things. I think minimally we need > to include info on: > - how to look up the citation (DOI, arXiv id, in a bibtex file, ...) > - how to display/export the citation (parens, footnote, in-text, ...) > - a list of properties (incl. at least pre- and post-note) > - (of course) the citation key > > So maybe: > > [cite:lookup-type:display-type:key:prop1=val1,prop2=val2] I favor [cite:PROPERTIES] over [[cite:PROPERTIES]], because the latter (link syntax) implies a (optional) description part. I don't think a description is ever meaningful in citations. Also, as I already mentioned, link syntax is already overloaded: there are many types of links and the link transcoder function in export back-ends is generally one of the most complicated to write (along with tables). Regards, -- Nicolas Goaziou