From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: org-cite and org-citeproc Date: Thu, 02 Apr 2015 08:57:08 -0700 Message-ID: <87oan6ed63.fsf@berkeley.edu> References: <87twx5hs2x.fsf@berkeley.edu> <871tk560p3.fsf@delle7240.chemeng.ucl.ac.uk> <878uedgeuq.fsf@berkeley.edu> <87iodh55b5.fsf@alphaville.usersys.redhat.com> <874mp0hlth.fsf@berkeley.edu> <87h9szg8io.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45348) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YdhVA-0004JT-Tc for emacs-orgmode@gnu.org; Thu, 02 Apr 2015 11:57:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YdhV7-0003Cb-M5 for emacs-orgmode@gnu.org; Thu, 02 Apr 2015 11:57:52 -0400 Received: from plane.gmane.org ([80.91.229.3]:40204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YdhV7-0003CG-FH for emacs-orgmode@gnu.org; Thu, 02 Apr 2015 11:57:49 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YdhV5-0007Sg-Q6 for emacs-orgmode@gnu.org; Thu, 02 Apr 2015 17:57:48 +0200 Received: from c-67-169-117-151.hsd1.ca.comcast.net ([67.169.117.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Apr 2015 17:57:47 +0200 Received: from richard.lawrence by c-67-169-117-151.hsd1.ca.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Apr 2015 17:57:47 +0200 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: emacs-orgmode@gnu.org Hi Tom and all, tsd@tsdye.com (Thomas S. Dye) writes: >> OK, I see, that makes things clearer. Would it make sense to have two >> keywords, say LATEX_CITE_STYLE and CSL_FILE or similar, so that the >> style can vary independently when exporting to LaTeX vs. non-LaTeX? I'm >> thinking it will be tricky to come up with a single set of values for a >> CITATION_STYLE keyword that can be correctly mapped to both kinds of >> backend. Or maybe CITATION_STYLE should have "sub"-keywords, like >> >> #+CITATION_STYLE: biblatex:authoryear csl:chicago-author-date.csl > > Won't the backends sort this out without the additional mapping? Surely they could, but I guess I'm unclear on how that should happen. Org could keep a variable mapping citation styles to default values for the respective backends, like: (defcustom org-cite-citation-styles '(("author-year" (biblatex-pkg-args "citestyle=authoryear,bibstyle=authoryear") (csl-file "/path/to/chicago-author-date.csl")) ...)) so in a document, you could just write #+CITATION_STYLE: author-year or similar. Is this what you have in mind? That seems like a good way to provide reasonable defaults using a high-level label. But I think using a high-level label like this will underdetermine the actual style to use (on both sides, I assume); and the problem is that if we make the labels more fine-grained, there's no longer any guarantee that, for a given style label, a suitable style file will be available on both LaTeX and non-LaTeX backends. There obviously needs to be some mechanism so authors can specify their citation style quite precisely for the backends they are interested in. (Maybe just customizing this variable would do the trick.) But what should the fallback mechanism look like when a particular style does not specify the required information for a given export backend? E.g., if CITATION_STYLE is X and we're exporting to HTML, but the entry in org-cite-citation-styles does not specify a CSL file for style X? Would it be enough to have a single 'default clause or similar in org-cite-citation-styles to use in that kind of case? Best, Richard