Hi Avram, Avram Lyon <ajl...@gmail.com> writes:
> On Mon, Mar 2, 2015 at 7:16 PM Richard Lawrence < > richard.lawre...@berkeley.edu> wrote: >> >> Is there any reason to go with citeproc-java over a different CSL >> implementation, like citeproc-js or pandoc-citeproc? I am a little >> nervous about shelling out to something that sounds it like it requires >> loading the JVM... > > citeproc-java just calls citeproc-js from Rhino or Nashorn, so there's > little reason to go with citeproc-java for any application not already > running on the JVM. Hmm, good to know. > Zotero is indeed using citeproc-js directly from XULrunner/Firefox, and > that is the best-supported usage of the library. > > If you're looking for something with citation management and CSL proessing, > perhaps zotxt is best. If you just want CSL processing, it would be best to > run citeproc-js by itself (there is a citeproc-node, but it's not quite > plug-and-play). That sounds right. And I agree with Aaron that we probably don't want a hard dependency on Zotero on the output side, so maybe citeproc-js is the way to go. On the other hand, as Aaron points out, citeproc-java has a BibTeX parser, and citeproc-js doesn't look like it would be easy to run from the command line...some sort of JS engine is required in addition to citeproc-js itself. I wonder if citeproc-js would run under Guile?? Maybe that would be the easiest way to turn citeproc-js into a lightweight command line utility that Org (and hence Emacs) could feel good about depending on. Best, Richard
