From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erik Hetzner Subject: Re: Citations, continued Date: Mon, 02 Feb 2015 07:45:24 -0800 Message-ID: <54cf9b97.0284440a.4361.3215@mx.google.com> References: <87vbjmn6wy.fsf@berkeley.edu> Reply-To: Erik Hetzner Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54491) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YIJBv-0004J8-80 for emacs-orgmode@gnu.org; Mon, 02 Feb 2015 10:45:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YIJBr-0000D2-Ot for emacs-orgmode@gnu.org; Mon, 02 Feb 2015 10:45:34 -0500 Received: from mail-pa0-x233.google.com ([2607:f8b0:400e:c03::233]:58191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YIJBr-0000CS-Fy for emacs-orgmode@gnu.org; Mon, 02 Feb 2015 10:45:31 -0500 Received: by mail-pa0-f51.google.com with SMTP id fb1so83911196pad.10 for ; Mon, 02 Feb 2015 07:45:29 -0800 (PST) In-Reply-To: <87vbjmn6wy.fsf@berkeley.edu> <87ioflmgkc.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 Cc: emacs-orgmode@gnu.org On Sat, 31 Jan 2015 at 10:26:05 PST, Richard Lawrence wrote: >=20 > Hi all, > > [=E2=80=A6] > > As I mentioned in the earlier thread, I think the Pandoc syntax is a > good place to start, and I think it would be valuable to have the two > syntaxes be compatible. But even Pandoc's citation syntax might not be > general enough to satisfy everyone's needs, so the first step for > introducing citation syntax to Org should be compiling a list of all the > things such a syntax should represent. Hi Richard, It would probably be worth reviewing the discussions that led to the pandoc citation syntax: https://groups.google.com/d/msg/pandoc-discuss/v54VxMXtoWM/7ezu4xDSN8gJ Of the requirements you later mentioned: > 1) a database key that references the cited work > 2) prefix / pre-text > 3) suffix / post-text > 4) references to page/chapter/section/whatever numbers and ranges. > This is likely part of the prefix or suffix, but might be worth > parsing separately for localization or link-following behavior. > 5) a way of indicating backend-agnostic formatting properties. > Examples of some properties users might want to specify are: > - displaying only some fields (or suppressing some fields) from a > reference record (e.g., journal, date, author) > - indicating that the referenced works should *only* appear in > the bibliography of the exported document (equivalent of LaTeX > \nocite) pandoc syntax handles 1, 2, 3, 4 (locator, which is separate from suffix) and some of 5 (author suppression; I=E2=80=99m not sure the use cas= es for journal/date/etc. suppression). It does not handle \nocite, but this is something that they have discussed in the past and could easily be supported in org-mode using, e.g. a #+NO_CITE block. Personally I feel this covers the 99% of uses while being human readable and writable. I agree that citekey management is something that should be handle separately, as this will depend on the backend (bibtex file, zotero, etc.) Whether these citekeys are also links doesn=E2=80=99t really matter t= hat much either and could depend on the backend. best, Erik -- Sent from my free software system .