From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: org-cite and org-citeproc Date: Thu, 02 Apr 2015 06:45:28 -1000 Message-ID: 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> <87oan6ed63.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56942) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YdiFe-00059O-Ou for emacs-orgmode@gnu.org; Thu, 02 Apr 2015 12:45:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YdiFW-0007QQ-9O for emacs-orgmode@gnu.org; Thu, 02 Apr 2015 12:45:54 -0400 Received: from gproxy1-pub.mail.unifiedlayer.com ([69.89.25.95]:35068) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1YdiFV-0007Oc-F5 for emacs-orgmode@gnu.org; Thu, 02 Apr 2015 12:45:46 -0400 In-Reply-To: <87oan6ed63.fsf@berkeley.edu> (Richard Lawrence's message of "Thu, 02 Apr 2015 08:57:08 -0700") 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 Hi Richard, Richard Lawrence writes: > 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? I was thinking the author would change CITATION_STYLE to fit the export, but I like your idea of setting up a universal configuration. As for a fallback mechanism, I like your idea of a user-configurable default. All the best, Tom -- Thomas S. Dye http://www.tsdye.com