emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Citation processing via Zotero + zotxt
Date: Thu, 03 Dec 2015 09:27:13 -0600	[thread overview]
Message-ID: <87lh9bh7se.fsf@fastmail.fm> (raw)
In-Reply-To: <87mvtsw3sp.fsf@berkeley.edu> (Richard Lawrence's message of "Wed, 02 Dec 2015 20:32:06 -0800")

Hi Richard, 

Richard Lawrence <richard.lawrence@berkeley.edu> writes:

> Hi Matt and all,
>
> Matt Lundin <mdl@imapmail.org> writes:
>
>> Given these complexities, it seems that if we went the zotero route we
>> could end up with a fairly large installation chain (firefox, zotero,
>> zotxt, plugin for zotero). And this would require installing items from
>> multiple, heterogeneous sources.
>
> Well, I would guess that many people who are interested in this already
> have Firefox installed, and after that, you just need to install two
> Firefox plugins: Zotero and zotxt.  Open a couple of links, give your
> permission, and that's it.
>
> If you're skeptical, I encourage you to try it:
>
> https://www.zotero.org/download/
> https://addons.mozilla.org/en-US/firefox/addon/zotxt/
>
> It's pretty easy.  And removing the plugins via about:addons is just as
> easy.

Thanks for the links. I'll try them out. But for bibtex users, wouldn't
there presumably have to be another zotero plugin that would allow for
live, automated importing of bibtex into zotero? (If anyone knows
whether such a plugin exists, please do let me know.)

> We have discussed this before, and in fact, I already started work along
> this route: see https://github.com/wyleyr/org-citeproc
>
> I stopped because people objected that distributing a Haskell program is
> too difficult.  Even if you can install pandoc-citeproc via your
> system's package manager, to build org-citeproc against it you need a
> complete Haskell build environment, which is (somewhat notoriously)
> difficult to work with, and too much to expect for the average person
> who just wants citation support in their Org documents.  Nor has anyone
> volunteered to take care of building and distributing a binary for every
> platform we'd want to support (including, I assume, Windows and OS
> X...).

Thanks for your work on this. I would agree that compile a haskell
program makes this a nonstarter for many users.

A thought experiment... Do we need a fork of pandoc-citeproc? Or could
we rather write an emacs-lisp wrapper that would feed citation data and
a bibliography to pandoc and receive a string containing citations
formatted in org syntax (one of pandoc's outputs). This could be done
via an export filter, with all the necessary manipulation being done on
the emacs/org side of things.

Pandoc is available in several linux distributions (in addition to the
deb file released by the project) and installers are available OS
Windows, so most people wouldn't need to compile it.

> The nice thing about Firefox (and these days, Emacs) is that it's a sort
> of cross-platform package manager.  If the citation processing
> dependencies are just Firefox plugins, they'll be much more accessible
> to a much wider group of people without a lot of work on our part.  So,
> that's why I'd prefer depending on Zotero to depending on something like
> org-citeproc or citeproc-node.

Javascript interpreters/engines are widely available for all platforms
if we create a wrapper script around citeproc-js. Node itself is also
easily available for most platforms. But we wouldn't need to set it up
as a node server à la citeproc-node.

Thanks so much for all your work on this. I'm happy to help out wherever
I can.

Best,
Matt

  reply	other threads:[~2015-12-03 15:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28 20:16 Citation processing via Zotero + zotxt Richard Lawrence
2015-11-30  8:12 ` Martin Yrjölä
2015-12-01  0:32   ` John Kitchin
2015-12-01  2:59     ` Richard Lawrence
2015-12-03  0:27       ` Matt Lundin
2015-12-03  1:41         ` Christian Wittern
2015-12-03 14:25           ` Matt Lundin
2015-12-03  4:32         ` Richard Lawrence
2015-12-03 15:27           ` Matt Lundin [this message]
2015-12-03 17:56             ` Richard Lawrence
2015-12-03 19:14               ` Thomas S. Dye
2015-12-03 22:05                 ` Rasmus
2015-12-03 20:45               ` Matt Lundin
2015-12-03 21:04                 ` Matt Lundin
2015-12-03 23:31         ` John Kitchin
2015-12-04  0:03           ` Rasmus
2015-12-04  1:49             ` John Kitchin
2015-12-05 21:18               ` Matt Lundin
2015-12-05 22:23                 ` John Kitchin
2015-12-04  2:06           ` Matt Lundin
2015-12-04 11:22             ` John Kitchin
2015-12-04 14:13               ` Matt Lundin
2015-12-05  1:23                 ` John Kitchin
2015-12-04  9:20           ` Eric S Fraga
2015-12-01  9:34     ` Ramon Diaz-Uriarte
2015-11-30 11:35 ` Eric S Fraga
2015-11-30 12:02   ` Ramon Diaz-Uriarte
     [not found] ` <CAN_Dec-JCmwQ2bc=U93rRaPMYyXOiN_PRbtyya9x396r3qqMrg@mail.gmail.com>
2015-12-01 12:12   ` Fwd: " Matt Price
2015-12-01 15:28     ` Eric S Fraga
2015-12-01 15:51       ` Richard Lawrence
2015-12-01 19:20         ` Matt Price
2015-12-01 21:34         ` Eric S Fraga
2015-12-01 21:51     ` Matt Lundin
2015-12-02 15:21       ` Richard Lawrence
2015-12-01 14:36 ` Rasmus
2015-12-01 19:37   ` Matt Price
2015-12-02 15:58   ` Richard Lawrence

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lh9bh7se.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=richard.lawrence@berkeley.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).