On Tue, Mar 3, 2015 at 9:28 AM Richard Lawrence < richard.lawre...@berkeley.edu> wrote: > > 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. >
I know that citeproc-js has tried to be engine-agnostic, so perhaps it can work with Guile. If not, you may also want to look at citeproc-hs and citeproc-rb, both of which are quite complete (they, I believe, pass the entire test suite) and which may be easier to bring in as dependencies (JS engines are still a rarer dependency than Ruby or Haskell).
