From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Citation syntax and ODT Date: Mon, 23 Feb 2015 15:25:39 -0800 Message-ID: <87fv9wrz0s.fsf@berkeley.edu> References: <87zj85s1vf.fsf@berkeley.edu> <54EAC71A.6080502@gmail.com> <87twycsg5a.fsf@berkeley.edu> <54EB6D6F.7060005@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37982) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQ2ON-0002Uy-QJ for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 18:26:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YQ2OK-0002tL-L5 for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 18:26:23 -0500 Received: from mail-pa0-f50.google.com ([209.85.220.50]:46557) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQ2OK-0002or-Fo for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 18:26:20 -0500 Received: by pabkx10 with SMTP id kx10so31154684pab.13 for ; Mon, 23 Feb 2015 15:26:18 -0800 (PST) In-Reply-To: <54EB6D6F.7060005@gmail.com> 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: vaidheeswaran.chinnaraju@gmail.com Cc: emacs-orgmode@gnu.org Vaidheeswaran C writes: >> But whatever style is chosen, I would still think that the fact that the >> citation is in-text rather than parenthetical, and that it has a prefix >> and suffix, should be represented in the output. > > 1. When you choose 'style' (Chicago etc.) wouldn't be one of in-text > or parenthetical already chosen for you? Stated other way, is the > choice between parenthetical or in-text document-wide or is it that > one could intermix the two styles in the same document. These could be intermixed in the same document. The document-level style determines how each type ultimately looks, but the choice of style is (mostly) independent of using parenthetical vs. in-text citations. > 2. Citation processor like JabRef just takes a cite-key. It doesn't > take a pre or post-note. So, the pre and post notes should be > spliced in to the exported document by the elisp module that > interfaces with the citation processor. Right. That's what I'm thinking, anyway. > If we are going to interface with a citation-processor, the best > course of action would be to have someone first 'gauge' the > capabilities provided by the citation processor and let that > experience inform what Org should aspire to do. Yes. Other people have more experience with this than me. But based on what Pandoc is able to do, I am pretty confident that everything that has been proposed could be handled by a CSL processor like citeproc-js (or Pandoc's own). The possible exceptions are the common prefix and common suffix in a multi-work citation, which I imagine would be easy enough to add to the output of the citation processor. Best, Richard