From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Citation syntax: a revised proposal Date: Tue, 03 Mar 2015 14:23:28 +0000 Message-ID: <87y4ne2m8v.fsf@gmail.com> References: <87k2zjnc0e.fsf@berkeley.edu> <87bnkvm8la.fsf@berkeley.edu> <87zj8co3se.fsf@berkeley.edu> <87ioezooi2.fsf@berkeley.edu> <87mw4bpaiu.fsf@nicolasgoaziou.fr> <8761aznpiq.fsf@berkeley.edu> <87twyjnh0r.fsf@nicolasgoaziou.fr> <87oaopx24e.fsf@berkeley.edu> <87k2zd4f3w.fsf@nicolasgoaziou.fr> <87egpkv8g9.fsf@berkeley.edu> <877fv6xfaq.fsf@gmail.com> <87twya2ak0.fsf@berkeley.edu> <87zj81aa97.fsf@nicolasgoaziou.fr> <87ioep2r6p.fsf@berkeley.edu> <87y4ngbgm7.fsf@nicolasgoaziou.fr> <87twy39qt2.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33759) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSnjf-00046k-13 for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 09:23:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSnja-0005mC-RW for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 09:23:46 -0500 Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:32923) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSnja-0005lD-Lm for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 09:23:42 -0500 Received: by widem10 with SMTP id em10so21850631wid.0 for ; Tue, 03 Mar 2015 06:23:42 -0800 (PST) In-Reply-To: <87twy39qt2.fsf@berkeley.edu> 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: Richard Lawrence , Nicolas Goaziou Cc: emacs-orgmode@gnu.org Hi Richard (again), 2015ko martxoak 2an, Richard Lawrence-ek idatzi zuen: >=20 > Could we guess the backend from the file extension on the BIBLIOGRAPHY, > to keep things simple here? I don't use a citation manager, so I don't > know if this is possible for anything other than Bib(La)TeX. >=20 > Also, as mentioned earlier, it would be really nice to support > org-bibtex as one of the reference database formats. (It's what I use, > so naturally it's what I think we should bless. :) This would allow > storing your reference database in-document. I too use org-bibtex, and I agree that in-document references would be nice. My skeletal implementation supports only org-bibtex at the moment. >=20 > Some things to think about: >=20 > 1) Is there ever a need to mix reference database formats in the same > document (e.g., zotero and org-bibtex)? (I would think not, but my > needs are simple.) I think this is most likely in collaborative situations: you have your carefully curated org-bibtex database, and your co-author sends you a bunch of references in some other database format. I think it=E2=80=99s pr= etty easy to support (convert everything to bibtex and concat it all together). >=20 > 2) Is there ever a need to mix multiple reference databases in the > *same* format (e.g., two different .bib files)? (I would think so, > given the existence in BibLaTeX of \addbibresource.) Certainly yes (this can be seen as a degenerate case of (1) above). >=20 > 3) If the answer to either 1 or 2 is yes, how should we decide > precedence between multiple reference databases? (Two databases might > contain the same key.) Initially I think an admonition of =E2=80=9Cdon=E2=80=99t do that.=E2=80=9D= Eventually, we could raise a warning (or error) on detecting multiply-defined keys. I think allowing, and trying to make sense of, multiple definitions is more trouble than it=E2=80=99s worth. --=20 Aaron Ecay