From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Some projects Date: Tue, 27 Oct 2015 12:01:54 +0000 Message-ID: <874mhczfil.fsf@gmail.com> References: <87wpub9jts.fsf@nicolasgoaziou.fr> <877fmazh2f.fsf@gmail.com> <87fv0x1t49.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35801) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zr2x2-0000Ri-IX for emacs-orgmode@gnu.org; Tue, 27 Oct 2015 08:02:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zr2wz-0005xP-Bn for emacs-orgmode@gnu.org; Tue, 27 Oct 2015 08:02:04 -0400 Received: from mail-wi0-x22d.google.com ([2a00:1450:400c:c05::22d]:38131) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zr2wz-0005x7-6s for emacs-orgmode@gnu.org; Tue, 27 Oct 2015 08:02:01 -0400 Received: by wicll6 with SMTP id ll6so156775895wic.1 for ; Tue, 27 Oct 2015 05:02:00 -0700 (PDT) In-Reply-To: <87fv0x1t49.fsf@berkeley.edu> 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 , emacs-orgmode@gnu.org Hi Richard, hi all, 2015ko urriak 26an, Richard Lawrence-ek idatzi zuen: >=20 [...] >> I was working on this rather intensively at one time, but I had to stop >> because other aspects of life intruded. I have just been coming back >> towards a situation where I can imagine myself having some (still small, >> but non-zero) chunks of time to devote to working on org. So I hope I >> will be able to pick this back up, but (regrettably) I=E2=80=99m not abl= e to >> make any promises. >>=20 >> Based on my recollection, here=E2=80=99s what the problems were when I s= topped: >>=20 >> - The only =E2=80=9Coff the shelf=E2=80=9D-capable citation processing l= ibrary that we >> found last time is in Haskell, which introduced some difficulties for >> distributing the resulting tool. I know some projects >> (e.g. git-annex) are written in Haskell and distributed as static >> binaries for windows/mac/linux/etc. We=E2=80=99d need to figure out how= to do >> this, or find another citation processing library in an >> easier-to-distribute language. >=20 > Yes, this is my understanding, too. In particular, there does not seem > to be an Elisp CSL library, and it would be a lot of work to write one. >=20 > The other CSL library that looks complete and usable is citeproc-js; but > like the Haskell library (pandoc-citeproc) it would need to be wrapped > somehow so that it can talk with Org. >=20 > It should be relatively straightforward for someone who knows Javascript > to write such a wrapper, if anyone wants to work on that. But this does > not really solve the problem with distribution.=20=20 It solves many of the hard problems though. Node.js is distributed as a binary for many platforms. We=E2=80=99d just have to direct users to install this in the =E2=80=9Cnormal way,=E2=80=9D and use the installed bin= ary to interpret the JS source. Whereas for haskell we=E2=80=99d be stuck building the binary ourselves, worrying about static linking/dll hell/32-bit dinosaurs/any of a half-dozen other problems that I don=E2=80=99t really understand. OTOH, pandoc-citeproc includes a bibtex parser; we=E2=80=99d need to write = a JS one and wire it up to citeproc-js. When I looked (quite some time ago), there did not seem to be any good bibtex parsing libraries in JS (and several third-rate ones). OT3rdH, responding to Matt=E2=80=99s message , > The disadvantage is that, from what I can tell, the javascript > implementation is the canonical version of citeproc, and the place where > improvements are pushed first. So, for instance, if one wanted to > implement an org-syntax output format for citeproc, citeproc-js would be > the most likely project to support that work. Pandoc can output org syntax, so it may be that we can just link with the main pandoc haskell library as well as pandoc-citeproc and solve this ourselves, without needing upstream support. --=20 Aaron Ecay